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

Document current authorization implementation #16722

Open
jalbinson opened this issue Dec 5, 2024 · 2 comments
Open

Document current authorization implementation #16722

jalbinson opened this issue Dec 5, 2024 · 2 comments
Assignees
Labels
platform Platform Team

Comments

@jalbinson
Copy link
Collaborator

jalbinson commented Dec 5, 2024

User Story

As a member of the ReportStream team, I would like to understand our current authorization strategy.

Description/Use Case

We need clear documentation of our current authorization strategy so we can make informed decisions going forward. We want to make sure we can support all the same use-cases as the existing system if we were to decide changes are warranted.

Dev notes

See all endpoints defined here

Acceptance Criteria

  • Document current authorization approach(es)
  • Document all endpoints authorization requirements including:
    • required scopes
    • required groups
    • any other checks (e.g.: client_id header, checking scope and group name formatting)
  • Document pros and cons of our current system
@jalbinson jalbinson added the platform Platform Team label Dec 5, 2024
@MichaelEsuruoso
Copy link
Collaborator

@MichaelEsuruoso
Copy link
Collaborator

Please add your planning poker estimate with Zenhub @adegolier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Platform Team
Projects
None yet
Development

No branches or pull requests

2 participants