Password-based Access

This page is written primarily for workshop leads (mentors and other partners) who will be inviting participants to sign in to the hub on the day of the workshop, without using GitHub for authentication.

Using the Openscapes 2i2c Hub in a workshop using a shared password

Instructions for workshop leads / mentors

If you are hosting a workshop that has a large number of participants, especially if workflows with GitHub are not part of the teaching curriculum, use the “shared password” access. This access method allows the instructors to share a single password with learners at the start of the workshop which they can use to log on the the Hub. Note that while this access method is nicely streamlined for workshop leads and participants, Hub admins do not have any way to contact the people added to the Hub. Thus, participants with this method are only allowed to stay in the Hub for one week before being removed.

Open an issue in the appropriate workshop-planning repository (NASA/NMFS [TBD]) outlining your workshop. This is for awareness across the Mentor community, and to help you plan and be supported by the admin team. Also add your workshop to the WorkshopRegistry (NASA/NMFS), and put “SinglePassword” in the 2i2c access type column. If you don’t have access to this sheet, reach out to the primary contact/admin for your hub.
Check with the primary contact/admin to ensure that the Hub image has the packages you need.
Reach out to 2i2c a month in advance via an email to support at 2i2c.freshdesk.com (example below), cc-ing the primary contacts for your hub, to tell them about the workshop date, start and end times, # of participants, and anticipated level of resources to be used. Also tell them that you would like to use the shared password hub, and provide a desired password.
Do not ask your workshop particants to request access via the access request Google form - it is not necessary for these types of workshops.

Example email to 2i2c for a workshop with shared password authentication

To: support [at] 2i2c.freshdesk.com
cc: Openscapes/NASA/NOAA primary contact

Hello,

The LP DAAC and Openscapes have an upcoming event where we are planning to use the Openscapes Hub. Here’s the main information:

The GitHub handle or name of the community representative: [github username], email@somedomain.com
The date when the event will start: July 7, 2024
The date when the event will end: July 7, 2024
What hours of the day will participants be active? 1:00pm - 5pm EEST (Athens, Greece).
Number of attendees: ~40
Resources per user: 14.8GB RAM / up to 3.7 CPU
The URL of the hub that will be used for the event: https://workshop.openscapes.2i2c.cloud/ (NASA) OR https://workshop.nmfs-openscapes.2i2c.cloud/ (NMFS)
Access method: shared password
Password choice: [YouChooseAPassword]

Thank you!

Erik

Email your learners to tell them that they will be able to access the Hub using the shared password during and for one week following the workshop, after which the password will be changed and the their home directories inside the Hub will be removed.

Example email to workshop particpants for a workshop with shared password authentication

To: workshop participants

Hello!

We are looking forward to hosting you for our upcoming workshop! We will do our work in the [NASA/NMFS]-Openscapes workshop hub:

https://workshop.openscapes.2i2c.cloud/ (NASA) OR https://workshop.nmfs-openscapes.2i2c.cloud/ (NMFS)

You will be provided a password at the beginning of the workshop which you can use to log in to the hub, along with your email address as your username. No prior setup is required. You will retain access to the hub, and the files you create within the hub, for one week after the workshop. After this the password will be reset and user directories will be removed.

Thank you, looking forward to the workshop!

Erik

During the workshop, instruct participants to log in using their email address as their username, and the shared password.

One week after the workshop, send another email to support at 2i2c.freshdesk.com (again cc the hub’s primarty contacts) and request that the password be reset and users’ home directories be removed from the workshop hub.

Instructions for Openscapes hub admins

This section is for Hub admins (Openscapes core team plus NASA/NOAA hub leads), who have access to the SharedPasswords-Openscapes.Cloud Google Sheet, and have close working relationships with 2i2c. These steps intentionally align with the steps outlined above for workshop leads, and are meant to be collaborative - experienced mentors will be more familiar with the process and need less help than people leading workshops using the hub for the first time.

Work with workshop lead in their issue (opening one if necessary) in the appropriate workshop-planning repository (NASA/NMFS [TBD]), and add it to the MainPlanning project board (example).
Review and record the workshop in the WorkshopRegistry (NASA/NMFS), and put “SinglePassword” in the 2i2c access type column in the appropriate row. All mentors should also have access to this sheet.
Help the workshop lead ensure that the resources in the hub are sufficient for the workshop’s needs. The default configuration should easily handle up to 100 particpants; more than that may require some work by 2i2c to scale up.
Record the new workshop password in the SharedPasswords-Openscapes.Cloud Google Sheet.
Seven days after the workshop finishes, coordinate with the workshop lead to make a request to 2i2c to change the password and remove user home directories from the workshop hub (definitely not the main hub). Record the password change in the Google sheet.