Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4105

Describe the Auth flows currently used for OpenCADC software

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      By completing and describing the existing flows, a better understanding of the work needed to integrate properly with SKA-IAM can be gained.

      Show
      By completing and describing the existing flows, a better understanding of the work needed to integrate properly with SKA-IAM can be gained.
    • Hide

      AC1: The authetication methods currently used by the communities utilising CANFAR and SI are understood and documented

      Show
      AC1: The authetication methods currently used by the communities utilising CANFAR and SI are understood and documented
    • 1
    • 0.5
    • 0
    • Team_PURPLE, Team_RED
    • Sprint 3
    • Hide

      See comments to issue for references to the writeup

      Show
      See comments to issue for references to the writeup
    • science-platform-services service-integration

    Description

      In order to understand the integration of SKA-IAM with other 0.1 components, the existing Auth flows used by CADC for CANFAR and SI must be understood and documented - ideally in a manner that maps similarities and differences to the AAI Design principles. This will provide insight to the work needed to integrate properly with the IAM platform.

      Attachments

        Issue Links

          is required by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-3880 Prototype AAI Infrastructure Component Token Flows in OpenCADC Services (CADC-12760 #5)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Funnel

          Spike - A time limited investigation to get some knowledge SP-4106 Technical debt IVOA GMS: spike to see how this could be made consistent with Authentication API

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                J.Jensen Jensen, Jens
                T.Dack Dack, Tom
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete14.0
                  Total14.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel