SAML: prefix for repeat email
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
No response
User Story
When a client is using the same IDP (with the same user) for diff sites (diff app SAML configs) in order to have granularity and avoid roles overriden, we need to include a prefix or mask in order to save the repeated user
Currently the repeated just prefix a random prefix, but clients may need a known prefix
Acceptance Criteria
The user is able to have the same user logging differently in many sites with the desired prefix
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
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 Java SAML authentication flow and locating the existing logic that assigns a random prefix when a user is repeated across configurations. Determine how a client-supplied prefix should be provided and validated, then verify that the same user can log in to multiple sites with distinct desired prefixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100