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

'You should use SSL (https) when you login with OAuth since CDF only allows redirecting back to an HTTPS site' #438

Open
annitya opened this issue Oct 20, 2020 · 2 comments

Comments

@annitya
Copy link

annitya commented Oct 20, 2020

By the recommendation of @muradsater we are forwarding tokens to our backend instead of using api-keys. This way no actual ouath-process is taking place, but our logs are still filled with the aforementioned warning.

I have quenched it with a nasty hack for now, but it would have been nice if the sdk-client supported token-forwarding in addition to api-keys and ouath.

@polomani
Copy link
Collaborator

polomani commented Nov 6, 2020

@annitya Hi! We are trying to not use gh issues here anymore.
Could you add a bit more information about this (maybe some code snippets) and post it here
https://www.cog.link/cdf-bug
?

@andersfylling
Copy link
Contributor

Just to let you know; you can disable github issues in the settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants