Login: unable to resolve anywhere but localhost?

[agilisium-github-admin]

How can we deploy on a remote system with the Oauth "localhost" callback restriction? For example, installing on EC2 server and accessing using external IP results in (Chrome): "This site can’t be reached localhost refused to connect. Search Google for localhost 3000 oauth Callback ..."

[sinergise-anze]

Unfortunately we don't have an easy solution for this at the moment. Authentication service can't allow arbitrary callback URLs for security reasons.

The other forks of this project that we know of replaced the login functionality entirely, which would probably make sense if you want to deploy the fork publicly anyway.

I will however keep this issue open so that we can maybe find a better solution / suggestion in the future.

[agilisium-github-admin]

Thank you - can you provide any references to these known forks / gists where this has been done for EOBrowser?

[sinergise-anze]

Sorry, no - I don't think any of them are public.

[maabdelghaffar]

If you replaced the login module, Is that gonna make issue with the WMS service provided by Sentinel-hub ? I think the login was needed to be able to use the WMS call.

[sinergise-anze]

If you use your own instance ids there should be no issues. You can either hardcode them to the app, or you can fetch them through API calls (similar to what EO Browser does when user logs in) - whichever suits your purpose best.