Child pages
  • WBS 2.3.2 Open OnDemand OAuth Design 2021-09-10 Meeting

Versions Compared


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


Agenda & Discussion


Review OOD web architecture:

  • Apache with mod_auth_openidc
  • Per-user Nginx (PUN) runs the user's dashboard and


  • applications


  • An OOD configuration selects OAuth tokens to pass to a PUN pre-hook that runs as root
  • The PUN pre-hook (script) does whatever it wants with the OAuth tokens


        • Could securely save them to files


        • owned by the user
        • Could put them in a token service


      Which OAuth Tokens


      What about Scott Sakai's concerns


      As an aside, a -major- hurdle to getting some other kind of authentication
      adopted is that it requires maintaining and running non-standard software
      in the critical path of authentication. If none of the
      capability-restricting features of SciTokens will be used, pursuing an SSH
      CA would speed adoption immensely. This is NOT an x509 PKI.
      Rather than requiring extra binaries on the system, to accept SSH
      certificates, modern OpenSSH requires one or two lines to the sshd config
      file, and a file with the CA's public key.
      I have developed an identity bridge that consumes Globus Auth access
      tokens, and produces SSH CA certificates, with the intent that it can be
      used for our OOD deployment. It's specific to SDSC's NSF resources, but
      the process might be adapted to something that would work XSEDE-wide.

      Try to fund OOD staff to help?

      • Use unspent funds

      Action Items

      •  xyz