bug: The Add Connection dialog in the Cred Issuance UX is kinda confusing because it is dual purpose for Sharing and Adding Connections.

[bkreiser]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When you click "Add Connection" in the Cred Issuance UX, it gives you a QR so that your mobile app can scan the connection to the server as well as in the next screen being able to add in the connection to the identifier that you created in the mobile app. Seems a little odd that both are optional. Maybe Add Connection should just be for adding a connection and not also for sharing a connection. Perhaps Sharing Connection should be a separate PopUp?

Expected Behavior

Add Connection should just be for adding. Not adding and sharing of Connection.

Steps To Reproduce

No response

Screenshots

No response

Smartphone (please complete the following information)

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Anything else?

No response

[iFergal]

I guess the motivation there was to keep the flow streamlined. The connection isn't fully there until both elements have been done, so people would otherwise think enough is done after adding the connection, but aren't aware of sharing the connection.

Anyway, we've been working on a "one-way scan" so you'll only need to scan the QR code in the web page and everything will be done. And I'm putting considerations into how this can be protected from spam, and have things like connection setup request notifications.

[bkreiser]

I see what you are saying with regards to needing both sides. I think a one way scan and a bit of a handshake would be the best. Currently it isn't obvious that a connection is two sided since you can complete the sides of the connection independent of one another.

[iFergal]

Yep, it's been long overdue. In Signify, it's one-sided and called a contact and not a connection. So it's like a phone book where you can't receive messages from the other party until you add them as contact.

Adding a higher level connection protocol has just been a TODO. I have this working on the main branch but the UI isn't integrated yet (should be this week) - but it'll be open to spam until that's nailed down, so I left KERIA default to not enabling it.