Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on how to manage admin access #26

Open
j08lue opened this issue Jan 30, 2025 · 1 comment
Open

Decide on how to manage admin access #26

j08lue opened this issue Jan 30, 2025 · 1 comment

Comments

@j08lue
Copy link

j08lue commented Jan 30, 2025

Dedicated GitHub team, or?

History: Current GitHub IdP based setup was chosen for our initial PoC.

Options

  1. Membership of a specified GitHub org + team --> GitHub is the sole IdP for admin access
  • Cons:
    • Only one IdP
  • Pros:
    • Solution is already around the corner
  1. Membership in a dedicated group in KeyCloak + policies
  • Questions:
    • Where would we define this configuration? GitOps config - would that mean to store admin emails publicly (in config YAML files in Git)?
      • Definition of groups could be via GitOps, but membership could be managed manually via admin interface.

Decision drivers

  1. Avoid repeated downtime (when adding a new admin)
  2. Avoid requiring code changes in all IdPs
@j08lue
Copy link
Author

j08lue commented Jan 30, 2025

Preliminary decision: Move forward with GitHub IdP solution for now

Possible to change later.

@j08lue j08lue closed this as completed Jan 30, 2025
@j08lue j08lue reopened this Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant