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

Update adminstrator access control document #385

Closed
cristiklein opened this issue Sep 1, 2022 · 1 comment · Fixed by #779
Closed

Update adminstrator access control document #385

cristiklein opened this issue Sep 1, 2022 · 1 comment · Fixed by #779
Assignees

Comments

@cristiklein
Copy link
Collaborator

Update this page to reflect how exactly access is being given to the super application developer and developers.

Notes from a previous meeting:

How are the Grafana roles used?

  • Overall mapping of Grafana roles:
    • Grafana admin: super application developer (configured by the admin)
    • Grafana editor: application developer (configured by the super)
    • Grafana viewer: any OpenID user
  • Onboarding process:
    • Super application developer logs in to Grafana via OpenID
    • Administrator logs in to Grafana via static admin user
    • Administrator promotes OpenID user to Grafana admin

How are OpenSearch roles user?

  • Configured via sc-config.yaml
  • Overall mapping:
    • dashboards_admin: administrator
    • dashboards_dev: Application developer
    • (OpenSearch lacks a notion of super application developer.)

How are Harbor roles used?

  • Pretty much like Grafana
  • Onboarding process:
    • Super application developer logs in to Harbor via OpenID
    • Administrator logs in to Harbor via static admin user
    • Administrator promotes OpenID user to Harbor admin
@vomba vomba self-assigned this Jan 24, 2024
@vomba vomba linked a pull request Jan 24, 2024 that will close this issue
2 tasks
@vomba
Copy link
Contributor

vomba commented Jan 24, 2024

Made a draft, not sure if that is enough, or requires more description.

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

Successfully merging a pull request may close this issue.

3 participants