OpenConext / OpenConext/OpenConext-dashboard
SURFsecureID fijnmaziger maken
Open
Nobody has claimed this yet.
needs discussion
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This issue is imported from pivotal - Originaly created at Mar 13, 2024 by Teun Fransen
- Om omhoog te gaan in LoA, heb je het token nodig van het LoA waar je naartoe gaat
- Om omlaag te gaan in LoA, heb je het token nodig waar je vandaan komt
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
No file, test, or entry point is named. Start by locating the SURFsecureID LoA transition and token-validation flow in the dashboard, then verify both directions: moving up requires the destination LoA token, while moving down requires the source LoA token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100