OpenConext / OpenConext/OpenConext-dashboard
Connection request from admin connects the wrong IdP
Nobody has claimed this yet.
- 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 Jun 18, 2024 by Bart Geesink
In the case where an admin has multiple IdP\'s, a connection request sometimes registers the wrong IdP.
- Admin tries to connect a service and does this in context of IdP A
- Connection request is made to IdP B
I have not yet been able to reproduce this issue fully. I have only seen the scenario where a ticket is created in JIRA. I suspect that the other scenarios (where connections happen automatically) experience the same issues.
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 tracing the admin connection-request flow when multiple IdPs are configured, using the JIRA-ticket scenario described in the issue as the first reproduction path. Compare it with the automatic-connection scenarios and verify that the IdP selected in the service context is the IdP used for the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100