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

Request a refresh token from Google #87

Open
m-mohr opened this issue May 26, 2024 · 0 comments
Open

Request a refresh token from Google #87

m-mohr opened this issue May 26, 2024 · 0 comments
Labels
upstream An issue with GEE or other upstream libraries, which we likely can't fix.

Comments

@m-mohr
Copy link
Member

m-mohr commented May 26, 2024

The Google OIDC implementation is not really standards-compliant. It's not an EE specific issue. I'm not sure where the right place would be to report this to Google, but it's documented on the web in various threads, some examples:

In OIDC an offline_access scope is usually supported, but Google added a proprietary access_type parameter instead.

openEO follows the OIDC specification and Google deriving slightly from it just makes it not work nicely together.
I don't want to hardcode specific behaviour into generic openEO libraries just for Google.

Something we could think about is Open-EO/openeo-api#534

@m-mohr m-mohr added the upstream An issue with GEE or other upstream libraries, which we likely can't fix. label May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream An issue with GEE or other upstream libraries, which we likely can't fix.
Projects
None yet
Development

No branches or pull requests

1 participant