Because I thought the above problem was an authentication problem, I asked for instance information at the above address after receiving an access token using Postman, referring to OAuth2 document.
And in this case, we were able to get a normal response.(401 error occurred when trying to access the instance without a token.)
When running EOBrowser locally, where should I set up where token information is received and maintained?
In Github’s Readme file,
I couldn’t find a place to set up authentication-related information because it was only mentioned in ‘Use Sentinel username and password’.
The version of EO Browser on Github is unfortunately not the latest one and has the deficient Readme.
We are planning on updating it to the latest version and with it the Readme should also be updated. It will be easier to make changes to the authentication.
Regarding the current version - the text below is a compilation of the answers gathered from the previous years and an explanation, what to change.
The assisted token method, providing an ability for non-authenticated access to your account, needs to be configured separately and is only available to our commercial customers, as mentioned in this answer.
In this Github issue it is mentioned that retrieving your own instances shouldn’t be a problem when you are logged in with your account.
The instance ids should be changed in src/store/config.js and in src/default_themes.json.
Unfortunately I didn’t have any luck with this.
Code that deals with authentication is in src/utils/auth.js and uses the environment variables defined in .env file (which is a copy of .env.example with the populated values). The variable that is used for autnehtication, is client id (REACT_APP_CLIENTID). The process of getting client id and client secret in described in Sentinel hub documentation.
I also tried changing the client id, I could log in, but haven’t had any luck with retrieving the data (client id and client secret created with Client grant type set to either Client Credentials or Implicit).
The next option is to use client id and client secret to get the token as described here.
Didn’t do that yet, but the changes would be done in src/utils/auth.js (and best to save the client id and client secret in .env file).
I got this far in the past few days but I didn’t want to put any more time into it since we will update the EO Browser code on Github soon. It became not-so-easy to do that because of all the improvements and updates on both EO Browser and Sentinel hub services. Hope it helps.