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

Document how to login into Keycloak with keycloak admin credentials #177

Closed
chinmayshrikhande opened this issue Apr 3, 2023 · 7 comments · Fixed by #327
Closed

Document how to login into Keycloak with keycloak admin credentials #177

chinmayshrikhande opened this issue Apr 3, 2023 · 7 comments · Fixed by #327
Assignees
Labels
documentation Improvements or additions to documentation kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@chinmayshrikhande
Copy link

Hi,

Currently, I have the local setup for tackle up and running. I was able to login from the tackle login page using the default credentials and was able to change my credentials.

I am facing a problem while logging into the keycloak administration console. I tried with the default credentials of (admin/admin) and also the changed credentials for tackle, but I am not able to login into keycloak.

Can you please help me with where can I find the credentials for keycloak.

Thanks!

@jwmatthews
Copy link
Member

@jmontleon @djzager @fbladilo @mansam can you help?

@jmontleon
Copy link
Member

jmontleon commented Apr 4, 2023

The admin password is randomly generated and stored in a secret. You can see the credentials by running something like:

oc -n konveyor-tackle get secret tackle-keycloak-sso -o go-template='{{ index .data "admin-username" | base64decode }} / {{ index .data "admin-password" | base64decode }}{{printf "\n"}}'

Or just oc -n konveyor-tackle get secret tackle-keycloak-sso -o yaml and manually decode the values.

@jwmatthews jwmatthews added the documentation Improvements or additions to documentation label Apr 4, 2023
@jwmatthews
Copy link
Member

Thank you @jmontleon

I added a 'documentation' label, so we can revisit project docs and be sure this information is clearly communicated for users.

@chinmayshrikhande
Copy link
Author

Hi @jwmatthews , @jmontleon,

Thank you very much for your help.
I was able to get the key-cloak credentials using following command:
kubectl -n my-tackle-operator get secret tackle-keycloak-sso -o go-template='{{ index .data "admin-username" | base64decode }} / {{ index .data "admin-password" | base64decode }}{{printf "\n"}}'

Thanks!

@jwmatthews jwmatthews changed the title Not able to login into keycloak using default credentials Document how to login into Keycloak with keycloak admin credentials Apr 6, 2023
@jwmatthews
Copy link
Member

Thank you @chinmayshrikhande for following back to confirm. I'll keep this issue open so we can use it to track updating the documentation.

@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Sep 18, 2023
@djzager
Copy link
Member

djzager commented Feb 14, 2024

/kind documentation
/priority important-soon
/triage accepted

@konveyor-ci-bot konveyor-ci-bot bot added kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 14, 2024
@jmontleon
Copy link
Member

Something like this is probably a little easier to read:
oc -n konveyor-tackle extract secret/tackle-keycloak-sso --to=-

@dymurray dymurray added this to the v0.5.0 milestone Jun 6, 2024
@dymurray dymurray moved this from 🆕 New to 🔖 Ready in Planning Jun 6, 2024
@jmontleon jmontleon linked a pull request Jun 6, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in Planning Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

5 participants