-
Feature
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
2022 Week 32-34 (from Aug 8)
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
- incorporates
-
KOGITO-6970 Add support for OAuth2 on Quarkus OpenAPI Extension
- Resolved
-
KOGITO-7057 [KSW][OpenAPI] - Add Token Propagation support to OpenAPI Extension
- Resolved
-
KOGITO-7263 [KSW-Guides] Orchestrating third party services with OAuth2 authentication
- Resolved
-
KOGITO-7058 [KSW][OpenAPI] - Add support for programmatic configuration of OidcClients for Oauth2
- Closed
-
KOGITO-7059 [KSW][OpenAPI] - Add OpenAPI identifier in the OAuth2 Quarkus properties to avoid naming clash
- Open
-
KOGITO-7060 [KSW][OpenAPI] - Use the OpenAPI Security Schema properties when no configuration is defined
- Open
- is blocked by
-
KOGITO-6811 OpenAPI Gen Migration Quarkus
- Resolved