ietf-tools / ietf-tools/dev-planning-dispatch
Prove datatracker can act as a 3rd-party IdP for Authentik
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Background: This project will need an OIDC provider for user logins before datatracker is likely to be converted to operating as an OIDC client against an external Authentik provider. Using datatracker as an OIDC provider was rejected because many or most users of this project will not need a datatracker account otherwise. For users who do have a datatracker account, it would be nice to allow them to log in without creating a new account and to reduce friction to correlating users with datatracker users.
We need to stand up an Authentik instance and configure it to use datatracker as a 3rd party IdP. We should also allow other 3rd party IdPs and also Authentik-local users. Identify changes to datatracker code and/or configuration to make this possible.
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
Begin by surveying datatracker's authentication and configuration surfaces, then review how an Authentik instance can use datatracker as a third-party OIDC identity provider. Define the required integration changes and configuration for third-party IdPs and Authentik-local users; completion should include a working proof of the login flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100