Replies: 1 comment 2 replies
-
|
I'm not super familiar with Okta, but I have a vague recollection from the last time I used it that there's some "public client" box (or something like that) that you need to check to enable the client to work without a secret. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am on Kargo 1.7.5, and I am not running any dex containers. I am using the API server to do my SSO as follows:
Followed this guide: https://docs.kargo.io/operator-guide/security/openid-connect/#registering-kargo-as-a-client
My settings are:
I can see the "SSO Login" button.
However,
I am getting this error when I try to login:
OIDC: {"cause":{"error":"invalid_client","error_description":"Client authentication failed. Either the client or the client credentials are invalid."},"code":"OAUTH_RESPONSE_BODY_ERROR","error":"invalid_client","status":401,"error_description":"Client authentication failed. Either the client or the client credentials are invalid.","name":"H5i"}I am wondering what else I could be missing. Is it the clientSecret? But I was reading that PKCE eliminates the need for that.
Beta Was this translation helpful? Give feedback.
All reactions