Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keycloak does not deal well when URLs containing the port 80 #27

Merged
merged 2 commits into from
May 13, 2021

Conversation

Sgitario
Copy link
Contributor

When using token, we might get:

 [keycloak] 05:36:26,827 ERROR [org.keycloak.services] (default task-1) KC-SERVICES0025: Error when validating client assertion: java.lang.RuntimeException: Token audience doesn't match domain. Realm issuer is 'http://keycloak-ts-alnohanwix.apps.ocp46.dynamic.quarkus/auth/realms/test-realm' but audience from token is '[http://keycloak-ts-alnohanwix.apps.ocp46.dynamic.quarkus:80/auth/realms/test-realm]'

When using token, we might get:
```
 [keycloak] 05:36:26,827 ERROR [org.keycloak.services] (default task-1) KC-SERVICES0025: Error when validating client assertion: java.lang.RuntimeException: Token audience doesn't match domain. Realm issuer is 'http://keycloak-ts-alnohanwix.apps.ocp46.dynamic.quarkus/auth/realms/test-realm' but audience from token is '[http://keycloak-ts-alnohanwix.apps.ocp46.dynamic.quarkus:80/auth/realms/test-realm]'
```
@Sgitario Sgitario force-pushed the add_workaround_keycloak branch from 86d23ea to 0bd42e0 Compare May 13, 2021 07:16
@Sgitario Sgitario merged commit f48b7da into quarkus-qe:main May 13, 2021
@Sgitario Sgitario deleted the add_workaround_keycloak branch May 13, 2021 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant