Repository navigation
|
I've been following several instructions to try to get an OIDC access token for the REST API. All of them are lacking in some way or another, and I haven't been able to get it working. This article on Medium suggests making a username/password, which is surely wrong as this is an M2M connection. This one provides what appears to be incorrect Client authentication instructions, as it calls for Authorization to be on for the client, which means Service account roles is greyed out. It suggests having Standard flow and Direct access grants enabled. This article from Cloud-IAM calls specifically for only Service account roles to be enabled, which seems correct, but is sparse on any other details. No matter what I try, with the {
"error": "invalid_client",
"error_description": "Invalid client or Invalid client credentials"
}And this in the logs: 2026-05-14 23:36:54,864 WARN [org.keycloak.events] (executor-thread-293) type="CLIENT_LOGIN_ERROR", realmId="4c505a5c-2b2e-4665-9e59-41b1f64cd578", realmName="ronin-public", clientId="null", userId="null", ipAddress="172.25.0.1", error="client_not_found", grant_type="client_credentials" I have checked several times to make sure that the client is correct, and have tried both the ID as well as the UUID, but I keep receiving client_not_found. Any help would be appreciated! |
Replies: 1 comment
|
Blah, turns out it's because I was using form-data as opposed to url-encoded form. |
Blah, turns out it's because I was using form-data as opposed to url-encoded form.