Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 8.1 Update 3 CR3, 8.1 Update 3
Affects Version/s: None
Component/s: Security
Labels:
None

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

8.1.z.GA
Git Pull Request:
https://github.com/wildfly-security/wildfly-elytron/pull/2334
Intelligence Requested:
Market:

Customer Impact:

Customer Escalated, Customer Facing

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Elytron OIDC client introduced parameter "provider-url" that should serve as an alternative to "auth-server-url" and "realm" parameters. But it doesn't cover all use cases, because while auth-server-url accepts relative URLs and takes HTTP headers "X-Forwarded-*" into account, the provider-ul does not.

clones

JBEAP-31272 [GSS](8.0.z) Provider URL of OIDC client does not work with relative URL nor with forwarded headers

Resolved

is incorporated by

JBEAP-31326 (8.1.z) Upgrade WildFly Elytron from 2.6.5.Final-redhat-00001 to 2.6.6.Final-redhat-00001

Resolved

is related to

ELY-2452 Wildfly OIDC with relative URL generates lots of keycloak requests

Resolved

Assignee:: Diana Krepinska

Reporter:: Ilia Vassilev

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/10/22 1:41 PM

Updated:: 2025/11/24 6:02 PM

Resolved:: 2025/11/21 1:02 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates