-
Notifications
You must be signed in to change notification settings - Fork 78
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
Login to SciServer directly #1999
Comments
brollb
added a commit
that referenced
this issue
Mar 18, 2021
brollb
added a commit
that referenced
this issue
Mar 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not a fan of the current approach to SciServer integration as it requires the user to enter his/her SciServer credentials into DeepForge. We should be able to update this to follow the flow used in http://turbulence.idies.jhu.edu/cutout/.
Namely, we should be able to direct the user to SciServer and redirect back to DeepForge on successful authentication.
The text was updated successfully, but these errors were encountered: