Hi, we're stuck on an upstream OIDC provider quest...
# ory-network
a
Hi, we're stuck on an upstream OIDC provider question (Scale plan). We need to federate to a customer's Okta app that's registered as a public client: token_endpoint_auth_method: none, PKCE, no client secret. We've confirmed it's genuinely public by hitting their token endpoint with just a client_id and a bogus code, which gives invalid_grant rather than invalid_client. Our
generic
provider has a secret stored, so Kratos sends client auth and Okta rejects the token exchange with:
Copy code
oauth2: "invalid_client" "Client authentication failed. Either the client or the client credentials are invalid."
Login and MFA succeed, only the code exchange fails. We can't clear the secret. A CLI patch setting it to "" fails with
Copy code
missing properties:
"client_secret"
, and blanking the field in the Console just keeps the old value. The Kratos schema looks like it should allow an empty string (no minLength, and only the key is required), so we suspect it's being dropped before validation. So: can Kratos do the token exchange with no client authentication, and if so how do we configure it? If it isn't supported, is it planned? Happy to share project details and timestamps privately. This is blocking a live SSO rollout. Also, minor: this provider has pkce: force, and your docs say that needs the suffix-less callback registered, but our customer registered the suffixed one and /authorize works fine. Which callback does force actually send?
m
Hello @abundant-battery-53585 That is strange! Ory Kratos expects
client_secret
as a required configuration property for upstream OIDC providers. So AFAICT it doesn't allow an empty string. Please open a support ticket via console.ory.com/support with all the details and we will get back to you ASAP - btw if you need support urgently please open a support ticket (or alternatively message [email protected]).