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

[Core feature] Expose raw claims in auth IdentityContext #2607

Closed
2 tasks done
katrogan opened this issue Jun 10, 2022 · 0 comments · Fixed by flyteorg/flyteadmin#447
Closed
2 tasks done

[Core feature] Expose raw claims in auth IdentityContext #2607

katrogan opened this issue Jun 10, 2022 · 0 comments · Fixed by flyteorg/flyteadmin#447
Assignees
Labels
enhancement New feature or request flyteadmin Issue for FlyteAdmin Service

Comments

@katrogan
Copy link
Contributor

katrogan commented Jun 10, 2022

Motivation: Why do you think this is important?

Now that admin service middleware is customizable, we should expose the raw claims returned by IDP providers for authenticated users to allow for custom authz rules in user's individual flyteadmin deployments.

Goal: What should the final outcome look like, ideally?

Passing along additional claims for use in service middleware should be doable

Describe alternatives you've considered

Not supporting this feature

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes

@katrogan katrogan added enhancement New feature or request flyteadmin Issue for FlyteAdmin Service labels Jun 10, 2022
@katrogan katrogan self-assigned this Jun 10, 2022
@katrogan katrogan changed the title [Core feature] Expose access token claims in auth IdentityContext [Core feature] Expose raw claims in auth IdentityContext Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request flyteadmin Issue for FlyteAdmin Service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant