-
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
Add support for default_client
from backend's OIDC provider info
#192
Comments
…t user config just one: use that one related to #192
`authenticate_oidc` first tries refresh token flow and falls back on device code flow related: EP-3700, #192
…ders, but user config just one: use that one related to #192
`authenticate_oidc` first tries refresh token flow and falls back on device code flow related: EP-3700, #192
…-auth add-oidc` and `oidc-auth` cli tools related: EP-3700/EP-3759
…ders, but user config just one: use that one related: EP-3700/EP-3759/#192
`authenticate_oidc` first tries refresh token flow and falls back on device code flow related: EP-3700, #192
…-auth add-oidc` and `oidc-auth` cli tools related: EP-3700/EP-3759
…ders, but user config just one: use that one related: EP-3700/EP-3759/#192
`authenticate_oidc` first tries refresh token flow and falls back on device code flow related: EP-3700, #192
now merged in master: initial experimental support for default_client, based on current proposal Open-EO/openeo-api#366 possibly to be revised when that PR is finalized |
Open-EO/openeo-api#366 was merged difference of this merged (draft) spec with original implementation: multiple default clients can be advertised by backend, so the current experimental implementation needs some work |
Initial experimental implementation with a single defaullt_client had to be adapted to multiple default clients from updated draft spec (Open-EO/openeo-api#366)
When backend-side updates are live (both dev and prod), I can fully test client side and merge |
Initial experimental implementation with a single defaullt_client had to be adapted to multiple default clients from updated draft spec (Open-EO/openeo-api#366)
backend part was deployed on dev, and new default_clients handling worked properly now waiting for deploy on prod |
Initial experimental implementation with a single defaullt_client had to be adapted to multiple default clients from updated draft spec (Open-EO/openeo-api#366)
Initial experimental implementation with a single defaullt_client had to be adapted to multiple default clients from updated draft spec (Open-EO/openeo-api#366)
driver changes were deployed in production |
see Open-EO/openeo-api#366 (also related: #191 , EP-3700)
The text was updated successfully, but these errors were encountered: