Child pages
  • WBS 2.3.2 OAuth SSH Planning 2019-06-06 Meeting
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Date

Agenda, Discussion, and Action Items

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

Background

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 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

Discussion

xyz

Next steps / actions

  • Meeting with which people
  • With what purpose

Attendees



  • No labels