spring-projects / spring-projects/spring-security
Retrieving authenticated user after receiving SAML from Microsoft Intra ID Saml2AuthenticatedPrincipal object is always null with spring 3
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Describe the bug
I am facing an issue retrieving the authenticated user after receiving SAML from Microsoft Intra ID as the Identity Provider (IdP). The Saml2AuthenticatedPrincipal object is always null.
To Reproduce
Steps to reproduce the behavior.
Expected behavior
non null object
Sample
A link to a GitHub repository with a minimal, reproducible sample.
Reports that include a sample will take priority over reports that do not.
At times, we may require a sample, so it is good to try and include a sample up front.
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
The report only identifies Spring Security, Microsoft Intra ID, and the Saml2AuthenticatedPrincipal object; it names no source file, test, or reproducible sample. Start by obtaining a minimal reproduction of the SAML login and tracing where the authenticated principal is retrieved. Done means the object is non-null after authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100