IDP Form Does Not Give User Context

wesleyboar commented 1 year ago

Overview

The IPD form (that I have a URL to) does not give user ample context to confidently make a decision.

What I Know

After chatting with the dev team, I understand this form is how the user chooses by what means they wish to authenticate. A typical user will see options "TACC Accounts" and "Login with Globus". A dev site user will see more options.

dev account options better ui

Basically this is like when signing in with Zoom, you have several ways to auth, and Zoom doesn't know which is suitable to your situation. But, unlike Zoom, there is no direct user account. This is the "or sign in with" and only that.

zoom or sign in with

What I Expect

Context. Why am I making a choice? And what choice am I making?

What I Propose

Important I am still learning TAPIS, so I can't offer anything definitive nor with any authority. There may be a semantic or technical problem with my proposals. Please share concerns, questions, etc. DesignSafe UI designer C.J. is helping me out.

New Form Description

Log in to TAPIS Select an account to continue

New Interaction Method & Layout

Instead of several radio buttons, have a button for each, (ideally) with an icon.

tapis login buttons v4

Technical Direction

The button icons would be c-button__icon--before (see "Icons"). This may required loading COre-Styles components/c-button.html.
The buttons I mocked up used min-width: 300px.
To submit the values with different buttons, but have unique user-facing text, use <button type="submit" value="…">Some Text</button> (source).

wesleyboar commented 1 year ago

I've started working on this:

54

wesleyboar commented 1 year ago

Completed via #54.

wesleyboar commented 1 year ago

Fixed by #57.

tapis-project / authenticator