Child pages
  • WBS 2.3.2 OAuth SSH Planning 2019-06-06 Meeting

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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

Drivers:

  • Products that have vendor/community support
  • Interfaces that simplify interactive access and that users prefer to use
  • Modern, standard, and ubiquitous user authentication and authorization mechanisms
  • Keep XSEDE innovative and leading in usability and ease of access thru the end of the program

Next steps / actions

...

We will probably need to meet with these people?

  • XCI management - What are we supposed to be doing? What is our mandate/scope for this?
    • E.g., just get through XSEDE-2, or look farther ahead?
  • SP PIs - They design & maintain the systems XSEDE provides access to and know the intended uses, users
  • Campus login server admins (CB-08) - They design campus login services & asked for SSO Hub access
  • Heavy SSH users on current XSEDE systems (SSO hub, others?)
  • Q: Should we also ask people who do computational science via other interfaces (Open OnDemand, Jupyter, cloud systems) how they do it and how they think it should be done on other systems?

With what purpose?

  • Confirm how SSH is currently used/needed on XSEDE SP systems, campus research systems.
  • Find out about future/upcoming systems and their interfaces.
  • Get a sense of the future needs for SSH access and how folks would LIKE it to work.

Discussion

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

Drivers:

  • Products that have vendor/community support
  • Interfaces that simplify interactive access and that users prefer to use
  • Modern, standard, and ubiquitous user authentication and authorization mechanisms
  • Keep XSEDE innovative and leading in usability and ease of access thru the end of the program

Presentation and user survey

  • Topic: The Future of SSH login 


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.

  1. Lee Liming and Jim Basney  Prepare public facing issue background slides 
  2. JP Navarro , Shava Smallen , and Kate Kaya Prepare survey(s) in the RSP targeting SSH users and service providers
  3. Shava Smallen Will try to get 2 PEARC19 BOFs, for this topic and for SP discussions on user needs

Timeline:

Attendees

...