-
Notifications
You must be signed in to change notification settings - Fork 17
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 OIDC client credentials auth? #324
Comments
This is not really feasible for web apps as client credentials need a client secret, i.e. you'd need to enter client_id and client_secret for every login and then keep the browser open. What's the usecase for a browser app? Usually a refresh token should cover a long enough time span... |
The typical use case is users that use client credentials based machine-to-machine auth for non-interactive workflows, but still want to be able to follow up e.g. batch job progress through the web editor. |
So effectively this would be implemented similar to a username (client ID)/password (client secret) login workflow? At some point we need to upgrade from the deprecated oidc-client-js to oidc-client-ts anyway, but it doesn't support client credentials either: https://github.com/authts/oidc-client-ts So it would need a whole new library and I'm not sure which one would cover all our use cases. So this is a major effort. |
I'm fine with the current assessment that the effort outweighs the added value at the moment. To the user interested in a feature like this:
|
I'm not sure if this is even remotely feasible, but we recently had several users asking about this, so just putting this here for future reference:
Is it possible to use the openEO web editor with service accounts (which only support the OIDC "client credentials" grant)?
The text was updated successfully, but these errors were encountered: