Make Keycloak the only authentication method
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Historically we deployed Traefik Forward Auth for auth on all our sites and later added Keycloak. Consquently, we have a mix of sites using TFA or Keycloak and clusters that are running the Keycloak operator but still relying solely on TFA.
We should do away with TFA in favor of Keycloak for all sites. Internal sites for Posit employees can have their Keycloak instance configured with Posit Okta as the identity provider.
This will give us a consistent auth story for both internal and external facing sites.
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
No files, tests, or entry points are identified in the issue. Start by inventorying how sites and clusters currently use Traefik Forward Auth or Keycloak, then define the migration scope; done means every site uses Keycloak and internal instances can use Posit Okta as their identity provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100