Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review Connection UI #26

Open
TimothyBJacobs opened this issue May 21, 2020 · 2 comments
Open

Review Connection UI #26

TimothyBJacobs opened this issue May 21, 2020 · 2 comments
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@TimothyBJacobs
Copy link
Member

We should ask for design review to make sure our UI is as understandable as possible.

This is the basic connection screen.
image

This is shown when you are connecting with a new application.
image

And this is what we show if you are connecting with a new application that is verified to be developed by the given uri.
image

The spec also recommends that we capture and display the following information as well.

logo_uri

URL string that references a logo for the client. If present, the server SHOULD display this image to the end-user during approval.

tos_uri

URL string that points to a human-readable terms of service document for the client that describes a contractual relationship between the end-user and the client that the end-user accepts when authorizing the client. The authorization server SHOULD display this URL to the end-user if it is provided.

policy_uri

URL string that points to a human-readable privacy policy document that describes how the deployment organization collects, uses, retains, and discloses personal data. The authorization server SHOULD display this URL to the end-user if it is provided.

And perhaps

contacts

Array of strings representing ways to contact people responsible for this client, typically email addresses. The authorization server MAY make these contact addresses available to end-users for support requests for the client.

@TimothyBJacobs TimothyBJacobs added good first issue Good for newcomers help wanted Extra attention is needed labels May 21, 2020
@TimothyBJacobs TimothyBJacobs added this to the Merge Proposal milestone May 21, 2020
@saylorrain
Copy link

This design looks good. It makes sense and flows well. One really small copy change on the "warning" notice. Remove the word "that" in the phrase "... an application that you haven't connected..." it is unnecessary. Everything else looks clean and it makes sense.

@TimothyBJacobs
Copy link
Member Author

Some notes from @georgestephanis was that we should consider flipping the verification UI. Instead of showing when a client is "verified" show a warning when the client is not verified. Like how browsers now handle SSL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants