-
Notifications
You must be signed in to change notification settings - Fork 181
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
Service Account Token Login #361
Comments
I did exactly that and "matched" additionally the ServiceAccount over the secrets attribute to the secret it self.
But I get still |
Hi @matthiasbaldi , I'm actively working on a patch for this issue. Please wait for an hour till I push it. |
Oh cool 👍 Thank you. |
Basically could you try create your secret with
Note that you don't need double quote for --from-literal param Also there's another issue around clusterRole, I'm pushing something to a patch branch... |
OK I pushed this branch #368, it's basically just readme updates with some examples. Feel free to read through it |
Hi @elieassi I included your suggestion in the Readme, thanks for the contribution. @matthiasbaldi new stable was released, please follow the troubleshooting part for keycloak. Please open a new issue if you're still blocked. |
If your cluster is Kubernetes 1.24 or a more recent release, even tho the clusterrolebinding role is executed correctly, a secret/token will not be automatically generated anymore for the serviceaccount.
You need to create a secret for the service account, the supplied commands plus creating the secret can be all achieved for example by the following file
The text was updated successfully, but these errors were encountered: