Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: 25.0.0.Beta1, 25.0.0.Final
Affects Version/s: None
Component/s: None
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly/pull/14655

As we developed WildFly Elytron and integrated in WildFly 11 and EAP 7.1 the specifications in use by Keycloak around OpenID Connect were very much in a state of ongoing development so at the time it made sense for the Keycloak project to handle the integration. The relevant specifications are now stable and it makes sense for individual projects to handle their own OIDC integration.

Another benefit mentioned from Stian is this would allow EAP / XP releases to be interoperable with other OIDC providers which may be required for both cloud and bare metal deployments.

Since the original WildFly client side adaptors were written for Elytron our integration has also progressed further, at the moment the installation of these adaptors requires security domains and realms to be defined before a deployment can be deployed.

The Keycloak adaptors support two different modes:

Managed
Deployment Configured

The native integration should support the same, cloud use cases are really showing a trend towards deployment configured at the moment.

In the case of deployment configured we should be able to eliminate the pre-wired configuration presently used. We have used this pattern already for microprofile-jwt by dynamically defining a virtual security domain.

Layering is also proving important, I would suggest a feature such as this should be in a dedicated subsystem "elytron-oidc" which will follow a similar pattern to the "microprofile-jwt" subsystem.

clones

WFCORE-5178 Native support for OpenID Connect

Resolved

is related to

WFLY-15260 Add the ability to secure the management console with OIDC

Closed

WFLY-15485 OIDC client adapter doesn't work correct with Bearer-only

Closed

WFLY-15866 OIDC client adapter doesn't support enable-basic-auth

Open

WFLY-15293 Enhancements to Elytron OIDC client subsystem implementation

Resolved

WFLY-15256 Add documentation for the Elytron OIDC client subsystem

Closed

WFLY-15257 Update the descriptions in LocalDescriptions.properties for the Elytron OIDC client subsystem

Closed

WFLY-15258 Add descriptions of the attributes in the Elytron OIDC client subsystem schema

Closed

WFLY-15259 Add tests to the Elytron OIDC client subsystem for attributes that allow expressions

Closed

WFLY-15297 Prevent OidcWithDeploymentConfigTest failing if docker is not available

Closed

WFLY-15298 Post WF Beta cleanups in elytron-oidc-client subsystem

Closed

WFLY-15292 Use OperationContext.getCurrentAddress() in SecureDeploymentDefinition in the OIDC subsystem

Closed

WFLY-15284 OIDC tests for logout and refresh token

Open

WFLY-15285 OIDC cluster test

Open

ELY-2234 Allow merge of resource & realm roles on OIDC Client

Resolved

WFLY-15885 OIDC client adapter should support multi-tenancy

Resolved

WFLY-15889 OIDC client adapter should support multi-tenancy

Closed

(12 is related to)

Assignee:: Farah Juma

Reporter:: Farah Juma

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2020/10/27 3:44 PM

Updated:: 2022/09/09 7:15 AM

Resolved:: 2021/09/16 11:01 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates