Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-2

[core] OAuth2 authorization flow in workflows

    XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • Major
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 32-34 (from Aug 8)

    Description

      Motivation

      Some operations require special permissions to get access to data from 3rd party services. OAuth2 is a common authorization protocol that allows a user to grant a third-party web site or application access to the user's protected resources, without necessarily revealing their long-term credentials or even their identity.

      Goal

      Enable OAuth2 authorization flow in workflows

      Scenarios

      • As a developer, I want my workflow to call a 3rd party service which is protected with an OAuth2 authorization protocol, without having to handle any token

       

      • As a developer, I want my workflow to call a 3rd party service which is protected with an OAuth2 authorization protocol, sending a token which should be used

      Expected outcomes

      Documentation describes use of this OAuth2 authorization flow on an example

      The authorization flow doesn’t require human interaction

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users KOGITO-6970 Add support for OAuth2 on Quarkus OpenAPI Extension

          • 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.
          • Resolved

          Feature Request - Feature requests from customers and/or users KOGITO-7057 [KSW][OpenAPI] - Add Token Propagation support to OpenAPI Extension

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7263 [KSW-Guides] Orchestrating third party services with OAuth2 authentication

          • 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.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-7058 [KSW][OpenAPI] - Add support for programmatic configuration of OidcClients for Oauth2

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-7059 [KSW][OpenAPI] - Add OpenAPI identifier in the OAuth2 Quarkus properties to avoid naming clash

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-7060 [KSW][OpenAPI] - Use the OpenAPI Security Schema properties when no configuration is defined

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open
          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-6811 OpenAPI Gen Migration Quarkus

          • 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.
          • Resolved

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: