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

Update the keycloak-admin-client doc to show a correct URL for legacy Keycloak #28426

Merged

Conversation

sberyozkin
Copy link
Member

The user has tried to run this tutorial against a WildFly based distribution, so had to figure out adding /auth was necessary, so the PR notes it, CC @michalvavrik

Quarkus Documentation automation moved this from To do to Reviewer approved Oct 6, 2022
[source,properties]
----
# WildFly based Keycloak distribution
quarkus.keycloak.admin-client.server-url=http://localhost:8081/auth
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this related to a specific Keycloak version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gastaldi No, all WlidFly based distributions have the /auth path segment

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is possible to configure Quarkus based distro to use /auth - but it is quite complex, so not really in scope of this guide

@sberyozkin sberyozkin merged commit 6abc77a into quarkusio:main Oct 6, 2022
Quarkus Documentation automation moved this from Reviewer approved to Done Oct 6, 2022
@quarkus-bot quarkus-bot bot added this to the 2.14 - main milestone Oct 6, 2022
@sberyozkin sberyozkin deleted the keycloak_admin_client_guide_url_fix branch October 6, 2022 15:20
@gsmet gsmet modified the milestones: 2.14 - main, 2.13.2.Final Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants