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

Define security strategy for API clients #96

Open
rareddy opened this issue Oct 26, 2023 · 1 comment
Open

Define security strategy for API clients #96

rareddy opened this issue Oct 26, 2023 · 1 comment
Assignees
Labels

Comments

@rareddy
Copy link
Contributor

rareddy commented Oct 26, 2023

Is your feature request related to a problem? Please describe.
Define how the security (AuthZ) is handled when a user using the API clients.

When a user is using the REST API layer, the JWT token will be passed in a Header, and user information can be gleaned from that along with roles that can be used for the gating of certain operations by the user. When user is using API client such as Python API or Go API from their Notebooks and Pipelines, a similar gating of operations need to be done.

Describe the solution you'd like
When a Notebook is running, it typically runs under a Service Account or User Account. A Service Account is pre-confiured with certain roles. The Python/Go clients need to glean this information from the executing environment they are in and use that user's credentials.

@rareddy
Copy link
Contributor Author

rareddy commented Oct 27, 2023

@danielezonca any guidance on this as to how the other components in the stack are managing similar requirements?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Status: No status
Development

No branches or pull requests

2 participants