Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 8.0 Update 12
Affects Version/s: 8.0.0.GA, 8.0.z.GA
Component/s: Security
Labels:
- one-off
- test_included

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.0.z.GA
Git Pull Request:
https://github.com/wildfly-security/wildfly-elytron/pull/2334, https://github.com/wildfly-security/wildfly-elytron/pull/2341
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.

is cloned by

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

Resolved

is incorporated by

JBEAP-31325 [GSS](8.0.z) Upgrade WildFly Elytron from 2.2.12.Final-redhat-00002 to 2.2.13.Final

Pull Request Sent

is related to

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

Resolved

Assignee:: Diana Krepinska

Reporter:: Diana Krepinska

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2025/10/13 10:12 AM

Updated:: 2025/11/20 6:38 PM

Resolved:: 2025/11/20 6:38 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates