OpenConext / OpenConext/Stepup-SelfService
Improve UI so users get feedback on why some token types are unavailable
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2
- Forks
- 5
- Avg merge
- 8d 13h
- Merged PRs (30d)
- 2
Description
@thijskh op slack:
Verwarring alom bij een gebruiker omdat die een nieuwe telefoon had en Tiqr token wilde registreren maar alleen de optie Yubikey kreeg (moest eerst nog oude Tiqr verwijderen). Misschien om mee te nemen bij SURFaccess. Iets verbergen obv voor gebruiker niet-evidente business rules zorgt voor verwarring. Misschien beter om wel weer te geven maar grayed out met reden dat je die niet mag kiezen?
Or maybe add an explicit option to replace an exisitng token?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the self-service UI that presents Tiqr and Yubikey token options, then trace the business rules that hide unavailable token types. Confirm whether the agreed outcome is to show disabled options with reasons, support replacing an existing token, or both; done means users understand why an option cannot be selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100