-
Notifications
You must be signed in to change notification settings - Fork 41
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
OIDC: support device code flow without secret or PKCE #225
Comments
It seems like authorization code flow also works without PKCE and client secret, so should be added, too. |
Open-EO/openeo-api#411 was merged and added default_client grants:
|
@aljacob the python client should now support default clients using OIDC device auth grant without PKCE nor client secret. Can FYI new feature is not in latest release (0.8.2), so use a recent git checkout (or a version >0.8.2 if that's available by the time you verify) |
FYI: I didn't add support for
I'm not sure if it's worth the trouble supporting at the moment (supporting it for device auth grant turned out more effort than I expected). |
In an effort to clean up some outstanding issues, I'm going to close this one. |
OIDC device code flow support: Python client assumes there are just two modes: with client secret or with PKCE, but apparently there are also implementations (e.g. KeyCloak 13+) that use neither. Python client should support these 3 (or more) properly
also see Open-EO/openeo-api#410
The text was updated successfully, but these errors were encountered: