Support a SAML Indentity Provider
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
Describe the solution you'd like
SAML is a common authentication method within enterprises and currently there is not an easy way to implement SAML auth flows with pinniped outside a standalone service provider like UAA.
Describe alternatives you've considered
Have currently implemented this using UAA, however this approach is complicated and deploying UAA into Kubernetes is not well documented and difficult for customers to navigate. UAA also has a lot of opportunity for something to be mis-configured and introduce security risks because of its vast capabilities. UAA's roadmap is also in doubt.
DEX has functional support for SAML but their documentation warns it's not actively being supported.
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 issue does not name repository files, tests, or entry points. Start by reviewing Pinniped's existing authentication flow and compare the UAA-based approach with the DEX SAML connector documentation linked in the issue; done means a supported SAML identity-provider flow with clear, secure configuration and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100