Uploaded image for project: 'mod-inn-reach'
  1. mod-inn-reach
  2. MODINREACH-1

Store an API Key and Secret Pair for Use by Associated INN-Reach Central Servers

    XMLWordPrintable

Details

    • Volaris

    Description

      Purpose/Overview:
      Provision OAuth 2.0 key and secret for INN-Reach Central Server(s) for use with Oauth2 authorization server for client_credential authentication and token generation.

      Requirements/Scope:

      1. Requirement: securely store a provided client key/secret pair
        • e.g. two UUID-like strings
      2. Requirement: provide a mechanism to invalidate a key/secret pair
      3. Requirement: support multiple "client" central servers (i.e. multiple "user" support)
      4. Requirement: One key/secret pair per "user"

      Approach
      TBD

      From development stand point:

      1) 

      2)

      3)

       

      Acceptance Criteria

      • AC: Secret is stored securely
      • AC: Keypairs can be deleted or marked as invalid
      • AC: Unique keypairs can be created and associated with a central server configuration (MODINREACH-34)
      • AC: Only one valid keypair per central server configuration

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-2672 Implement "Third Party" OAuth2 Token Endpoint for D2IR (INN-Reach)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            duplicates

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINREACH-34 Create Backend Model for Base INN-Reach Central Server Configuration

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is required by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINREACH-41 Provide API to Store an API Key and Secret Pair for Use by Associated INN-Reach Central Servers

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            requires

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINREACH-34 Create Backend Model for Base INN-Reach Central Server Configuration

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                andrii.khodyka Andrii Khodyka
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases