Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-774 Configure allowed OAuth flows per Service
  3. THREESCALE-1947

Configure OAuth flows in the UI

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • None
    • 2.4 GA
    • System
    • 5
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

    Description

      System UI should allow configuring the OAuth flows.

      Only when selecting OIDC authentication under Service > Integration > edit integration settings > Authentication

      When OIDC is selected then 4 checkboxes should be seen in Service > Integration > Edit APIcast configuration > Authentication Settings corresponding to:

      • standardFlowEnabled (Authorization Code flow) [selected by default]
      • implicitFlowEnabled (Implicit flow)
      • serviceAccountsEnabled (Client Credentials flow)
      • directAccessGrantsEnabled (Resource Owner Password Credentials flow)

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue THREESCALE-1951 CRUD for OIDC configuration of Proxy

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Sub-task - The sub-task of the issue THREESCALE-1949 Proxy, OIDC configuration model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-2072 Application update events trigger zync when first*traffic_at fields are updated

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              hramihaj Hery Ramihajamalala (Inactive)
              Jose Miguel Gallas Olmedo Jose Miguel Gallas Olmedo
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: