Skip to content
This repository has been archived by the owner on Sep 16, 2023. It is now read-only.

[Feature Request] handle non sts s3 #61

Open
alexisdondon opened this issue Oct 25, 2022 · 1 comment
Open

[Feature Request] handle non sts s3 #61

alexisdondon opened this issue Oct 25, 2022 · 1 comment

Comments

@alexisdondon
Copy link

Onyxia ui authenticate user based on oidc configuration. The oidc jwt let onyxia generate some temporary token on s3 if the s3 allow AssumeRoleWithWebIdentity operation.

This is not an operation that all s3 solution implement.

To let onyxia be opened to more customers and more s3 solutions, we could imagine a special configuration in the region where the administrator could specify sts or not sts enabled.

If sts enabled the flow is the one supported with AssumeRoleWithWebIdentity .
if sts not enabled, the ui shoud let user specify his user s3 configuration accesskey/secretKey.

This issue could be discussed to make a first minimalist viable proposition as the subject could be complex.
Especially thinking of this feature from a group perspective.

@fcomte
Copy link
Contributor

fcomte commented Nov 4, 2022

I think this feature request can be link with the subject to start a service with a service account in stead of personnal creds.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants