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

✨ Support auth scopes declared on the addon CR. #590

Open
jortel opened this issue Jan 5, 2024 · 0 comments
Open

✨ Support auth scopes declared on the addon CR. #590

jortel opened this issue Jan 5, 2024 · 0 comments

Comments

@jortel
Copy link
Contributor

jortel commented Jan 5, 2024

For consideration.

Support auth scopes declared on the addon CR. The scopes included in the addon token are currently hard-coded in hub. The purpose of limiting the addon (role) scopes is safety. Addon's make changes to the inventory grammatically and, as such, are a much higher risk of malicious activity and accidental damage to the inventory at scale.

Pros:

  • Not hard coded.
  • Declaritive.
  • Tailored to each addon's needs.

Cons:

  • Addon writer needs to know the scopes.

Example with currently mapped scopes.

auth:
  scopes:
    - applications:get
    - applications:put
    - applications.tags:*
    - applications.facts:*
    - applications.bucket:*
    - applications.analyses:*
    - identities:get
    - identities:decrypt
    - proxies:get
    - settings:get
    - tags:*
    - tagcategories:*
    - tasks:get
    - tasks.report:*
    - tasks.bucket:get
    - files:get
    - files:post
    - files:put
    - files:patch
    - rulesets:get
@jortel jortel changed the title ✨ Support auth scopes declared on the addon CR. This approach is better because: ✨ Support auth scopes declared on the addon CR. Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant