Hi, we are aware that this is not very clear, and we are working on a better explanation. I will send you a document that hopefully clarifies things shortly. If you can then comment on that, we will update our documentation.
Which issue are you experiencing regarding the authentication to openeo.vito.be? If you use the code with `authenticate_oidc` from the original post, your program should output a personalized link to https://aai.egi.eu/ which you can follow to login to your Terrascope/VITO account (via EGI Check-in/VITO).
> Is there a way to do this without manually entering the credentials each time?
Normally, if you use the default behavior of `openeo.connect( "openeo.vito.be" ).authenticate_oidc()` , the openEO python client will store "refresh tokens" locally on your system, which acts a bit like cookies in you browser: the next time you use `.authenticate_oidc()`, these refresh tokens will automatically log you in, without the need for manual entering of credentials.
So if you really have to enter your credentials "each time" as you mention, there is something a bit wrong. With the defaults, it should only be necessary to enter credentials every X weeks.
Do you work in an environment where you have a persistent home folder? Or do you use a worfklow (e.g. docker based) where you start from a pristine file system each time?
more info and tips about this can be found at https://open-eo.github.io/openeo-python-client/auth.html#authentication-for-long-running-applications-and-non-interactive-contexts
Terrascope utilise des cookies nécessaires. Afin d'optimiser votre expérience d'utilisateur sur notre site web, nous souhaitons également utiliser des cookies facultatifs pour lesquels nous demandons votre autorisation.
Comments
authentication for openEO on the python client
Hi, we are aware that this is not very clear, and we are working on a better explanation. I will send you a document that hopefully clarifies things shortly. If you can then comment on that, we will update our documentation.
Python client authentication
Hello, I am having the same issue on the authentication for openEO on the python client.
Can you refer me to a relate article or provide me a document?
Hi, Which issue are you…
Hi,
Which issue are you experiencing regarding the authentication to openeo.vito.be? If you use the code with `authenticate_oidc` from the original post, your program should output a personalized link to https://aai.egi.eu/ which you can follow to login to your Terrascope/VITO account (via EGI Check-in/VITO).
I am interested in…
I am interested in authentication to openeo.vito.be by inserting the credentials programmatistically.
Right now I use "authenticate_oidc", I follow the link and I connect to Terrascope/VITO account via D4SCIENCE.
Is there a way to do this without manually entering the credentials each time?
> Is there a way to do this…
> Is there a way to do this without manually entering the credentials each time?
Normally, if you use the default behavior of `openeo.connect( "openeo.vito.be" ).authenticate_oidc()` , the openEO python client will store "refresh tokens" locally on your system, which acts a bit like cookies in you browser: the next time you use `.authenticate_oidc()`, these refresh tokens will automatically log you in, without the need for manual entering of credentials.
So if you really have to enter your credentials "each time" as you mention, there is something a bit wrong. With the defaults, it should only be necessary to enter credentials every X weeks.
Do you work in an environment where you have a persistent home folder? Or do you use a worfklow (e.g. docker based) where you start from a pristine file system each time?
more info and tips about this can be found at https://open-eo.github.io/openeo-python-client/auth.html#authentication-for-long-running-applications-and-non-interactive-contexts