-
Notifications
You must be signed in to change notification settings - Fork 4
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
Default Keycloak setup is not IS-10 compliant #56
Comments
It seems I was wrong on the second point - for the example flow in INFO-002 a client_secret shouldn't be generated as a token_endpoint_auth_method is present in the request, so Keycloak was following that correctly. Having a worked example of how to request a token in the case where a client_secret is generated/required would probably be useful (i.e. what changes are there in the client_assertion_type and client_assertion etc for this case) |
The If a new example is required, I would suggest adding a confidential Controller, using |
I think the client secret issue is actually a confusing contradiction between: and https://specs.amwa.tv/is-10/releases/v1.0.0/docs/4.2._Behaviour_-_Clients.html#client-credentials The former says "an Authorization Server MUST generate a Client ID and, in the case of a confidential client, a client secret", but the latter discusses and prefers the Because most people read the spec in order, they will read the 4.1 text before the 4.2 section. |
Part of wider review of BCP-003 suite. |
If a Keycloak server is set up following the INFO-002 guidance, the result will not be compliant with IS-10. In particular, for this section:
https://specs.amwa.tv/is-10/releases/v1.0.0/docs/4.1._Behaviour_-_Authorization_Servers.html#client-registration
The default Keycloak behaviour does not require an Initial Access Token for client_credentials registrations. Also, unless I'm misunderstanding what is meant, it doesn't generate a client_secret for client_credentials registrations either.
It would be good to add some guidance on how to make Keycloak compliant to IS-10 to the INFO-002 text, assuming it is possible to make it compliant.
The text was updated successfully, but these errors were encountered: