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

API Key Based Downloads

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None

      Problem: As an End User, the difficulty of using MyProxy certificates to download data can be quite frustrating. Certificates can expire, organization firewall rules can block access to the MyProxy port, OpenJDK vs Oracle Java issues, etc...

      Problem: As a Devops person on the ESG Gateway, it is difficult and confusing to get all the certificates correctly created for MyProxy setup correctly. We also have MyProxy as a dependency on our Database's openid and password fields.

      Acceptance Criteria:

      Todo list:

      Update Gateway auth-z (SAML) to support OpenID and Tokens
      Update TDS to work with OpenID and Tokens.
      Refactor WGet scripts to use tokens only.
      Remove MyProxy VM.
      Update scripts to remove MyProxy configuration.
      Remove mutual auth-n from Gateway and TDS (Apache and Gateway Spring Security).
      Continue to support OpenID auth-n in ESG Gateway and TDS.

              Unassigned Unassigned
              ejn Eric Nienhouse
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: