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

Simpler sign-on process for demo hub #403

Closed
3 tasks
sean-morris opened this issue May 14, 2021 · 5 comments · Fixed by #418
Closed
3 tasks

Simpler sign-on process for demo hub #403

sean-morris opened this issue May 14, 2021 · 5 comments · Fixed by #418
Assignees
Labels
Enhancement An improvement to something or creating something new.

Comments

@sean-morris
Copy link
Contributor

sean-morris commented May 14, 2021

Summary

There is a conversation between Eric V, Yuvi and myself regarding allowing a simpler login process to the demo hub for instructors who are wanting to explore how the 2i2c hubs are working.

User Stories

  • Currently, the demo hub is configured to use google-oauth2 which, of course, requires a google account to use. This can be a bit ackward when a potential instructor's work email address is not associated with Google. We are wanting to enable logging into the demo hub with a username and password(possibly default password) for a user who wants to see the hub in action. This is how the workshop datahub is working.

Acceptance criteria

  • I assume acceptance is a consensus moment about moving forward from the group. Once we are finished, anyone can "log" into the demo hub with any username and a default password.

Important information

Tasks to complete

  • Discuss / decide on whether or not this is the way forward
  • Implement the change to the demo hub
  • Re-deploy demo hub
@sean-morris sean-morris added the Enhancement An improvement to something or creating something new. label May 14, 2021
@yuvipanda
Copy link
Member

The berkeley workshop hub uses DummayAuthenticator with a simple password. It has restrictions on maximum active users as a way to control cost. I propose we do the same here.

@yuvipanda
Copy link
Member

This is also just for demo.cloudbank.2i2c.cloud, so will mostly just be used by DSEP folks.

@choldgraf
Copy link
Member

Fine with me - we can always change the password if people are abusing it. I think this hub should generally be "no promises" from us anyway

@yuvipanda yuvipanda self-assigned this May 17, 2021
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue May 17, 2021
Uses a 'database' connector[1] with auth0 to provide
username / password authentication.

demo.cloudbank.2i2c.cloud is now moved over to this,
making it easier for people to give demos. This also
removes any current restrictions on who can log in,
and opens it up to everyone. We add some resource
restrictions to match this.

Fixes 2i2c-org#403

[1]: https://auth0.com/docs/connections/database
@yuvipanda
Copy link
Member

ok I've actually instead added a signup with username / password + login there.

image

This uses auth0 as well - https://auth0.com/docs/connections/database.

@ericvd-ucb @sean-morris Once we switch, users who are currently using the google auth will need to sign up with a username / password to log in. Do you think you can communicate this to them?

yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue May 17, 2021
Uses a 'database' connector[1] with auth0 to provide
username / password authentication.

demo.cloudbank.2i2c.cloud is now moved over to this,
making it easier for people to give demos. This also
removes any current restrictions on who can log in,
and opens it up to everyone. We add some resource
restrictions to match this.

Fixes 2i2c-org#403

[1]: https://auth0.com/docs/connections/database
@yuvipanda
Copy link
Member

Documentation at pilot.2i2c.org also needs to be updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants