Loading...

XML

Word

Printable

Epic Name:
OAuth 2.0 in OpenAPI CRD
Blocked:
False
Blocked Reason:
None
Ready:
False
3Scale PT Tested upstream:
Not Started
3scale PT Docs:
Not Started
3scale PT Product Specs:
Not Started
3scale PT Product Update Ready:
Not Started
3scale PT Released In Saas:
Not Started
3scale PT Verified Product:
Not Started
Doc Version/s:

2.14.0 GA, 2.15.0 GA
Epic Status:
To Do
Hierarchy Progress Bar:

50% To Do, 0% In Progress, 50% Done
Target Release:

2.14.0 GA
Git Pull Request:
https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1545, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1620
Intelligence Requested:
Market:

Currently, the OpenAPI CRD only supports the apiKey security scheme.

This RFE is asking to also introduce support for Oauth2 with any OAuth flow type.

is related to

THREESCALE-10519 OAS without sec. section doesn't emit error message OpenAPI CR contains oidc section

relates to

THREESCALE-10518 Operator crash - OpenAPI CR doesn't create correct backend usage section in Product CR

THREESCALE-10523 oidc in OpenAPI CR ignores some attributes for Product CR

THREESCALE-10524 cannot set multiple auth flows in OpenAPI CR

links to

RHEA-2023:119803 Release of 3scale operator 0.11.8 for RHOAM - Containers