Copy and component updates to 2FA set up pages #10637
Replies: 4 comments 2 replies
-
|
@ajacobs21e Thanks! I really like it! It'd be great to update all components to the PF4 ones. The specific text below the title seems promising as well when the user is properly informed about the required action. However, it'd be great to find out what intention is behind keeping the login theme in the current state; I'm not sufficiently familiar with it. @ssilvert @stianst Do you have a chance to share your opinion? |
Beta Was this translation helpful? Give feedback.
-
|
@mabartos LGTM |
Beta Was this translation helpful? Give feedback.
-
|
@ssilvert Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Download buttons in the Keycloak Version would be very helpful, if the app name, the image and download URL is configurable. Example: Would be displayed as: 1. Install an authenticator app Additional note: I would switch one time code and device name input field. Otherwise, the user could think about the device name while the code changes. If device name is typed first, then the user can enter the code and send it immediately. |
Beta Was this translation helpful? Give feedback.
-
|
@jbman Is the device name editable in Keycloak after setting up the authenticator? The one-time code is first since step 3 is to enter this code and it is the required field, whereas device name is optional. Having the required field first is a better hierarchy. |
Beta Was this translation helpful? Give feedback.
-
|
@ajacobs21e, the device name is not editable currently. Below you see an example where I named the device 'My mobile'. The one-time-code changes every 30 seconds while you have the dialog open. If you enter the code first and device name second, the code displayed on your device could have already changed . That's why I recommend to put the one-time-code input field last, even if device name is optional. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The Red Hat downstream version of the mobile authenticator setup pages underwent a copy review by a Content Strategist. These pages were also designed with the latest PatternFly components. We are contributing these changes upstream.
Most changes are text updates and updating to newer PatternFly components (that may not have been available when these pages were originally built).
The Red Hat version has download buttons to the Android and Apple app stores (note B) - is this a feature that Keycloak would want as well?
#8806
Beta Was this translation helpful? Give feedback.
All reactions