Uploaded image for project: 'Gateway'
  1. Gateway
  2. GTWY-5318

Login via ORCID OAUTH 2.0 SSO Providers

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Standard Standard
    • None
    • None
    • None
    • None
    • 8
    • Sprint 260, Sprint 264

      Problem:

      The OpenID protocols have been deprecated.

      Acceptance Criteria:

      Contact GS to set up accounts to use ORCID OAUTH 2.0 service(s) for production, prototype and localhost instances for CDG, GDEX, DASH Repo.
      Add registration workflow to support requiring first name, last name, email for new user accounts.
      Place ORCID Login behind toggle.

      Then:

      Create tickets for GitHub, Google integration.
      Identify direction for authorization on TDS.

      General:

      Migrate the gateway to use OAUTH 2.0 as an authentication mechanism via the google, github and ORCID sso providers.
      Move earthsystemgrid.org OpenIDs to local user/password. Encourage users to use external login provider (and not local).

      Consider: TDS download use case.
      Note: This related to Gateway branding and the URL we use for identity, etc. Ie, we want to move away from earthsystemgrid openids...

      Consider: DASH Service desk logins and integration.

              nhook Nathan Hook
              ejn Eric Nienhouse
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: