Date

Agenda, Discussion, and Action Items

Discuss how we will engage others in XSEDE to evolve existing interactive login capabilities.

Background

Which use cases does this concern?

Which use cases does this NOT concern?

Current components:

  1. SP login nodes with GSI OpenSSH server and Globus client (from Globus)
  2. SSO hub with OpenSSH using Kerberos and xsede-user-tfa PAM modules (from XSEDE) and Globus GSI OpenSSH client (from Globus)
  3. Any command line client running any SSH client accessing the SSO hub

Possible future components:

  1. SP login nodes with GSI OpenSSH server and Globus client (from the Grid Community Toolkit)
    1. Q: Who would be providing the support for this software (GSI* from GCT)?
  2. Any command line client running any SSH client with the Globus SDK (a.k.a. Globus Auth OpenSSH)
  3. Any command line client running any SSH client with web based login service (a.k.a. Lee's pilot)
  4. Jupyter based browser login client
    1. Lee thinks Jupyter isn't a login client. (It doesn't provide a terminal interface on the compute system.) True or false?
    2. If the above is true, is the idea that users will no longer need terminal interfaces on XSEDE systems? That seems unlikely given the current systems.
  5. Open OnDemand

We will probably need to meet with these people?

With what purpose?

Discussion

We don't know where SSH access is going and need to engage users and XSEDE stakeholders to identify a path forward.

Needs that are driving this discussion:

Next steps / actions

We will survey users and SPs and hold a PEARC19 BOF so that by early Fall 2019 we have the input needed to prepare an XSEDE SSH futures plan.

Attendees