-
Notifications
You must be signed in to change notification settings - Fork 258
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
Support Client Configuration Endpoint #134
Comments
Not intentionally omitted!
Yes ! :-) — Roland |
Thanks @rohe. I'll work toward a pull request that you and others can weigh in on. |
We do have our own implementation of this, so I can give it a try. |
Eh, sorry. Misread the issue. I am not familiar with the usage of endpoints in this manner. |
It looks like this cannot be done in the current state of the |
Isn't this implemented in the oic/extension/providers.py code: At least it looks pretty similar. |
You are correct! The only documented method in OIDC specifications is I will give it a try later this week. |
http://openid.net/specs/openid-connect-registration-1_0.html#ClientConfigurationEndpoint
oic.oic.Provider:registration_endpoint works great, and the ClientRegistrationResponse includes the 'registration_client_uri'. However, if I issue GET requests to that URI, I usually get a 400 Bad Request response code. It looks like this is because the GET request is treated the same as a (new) Client Registration Request.
@rohe Is this "Client Read Request" functionality something intentionally omitted? Or would you welcome contributions to implement it?
The text was updated successfully, but these errors were encountered: