Skip to content
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

Consistency in handling the redirect urls from client #9

Closed
tecoholic opened this issue Sep 15, 2015 · 1 comment
Closed

Consistency in handling the redirect urls from client #9

tecoholic opened this issue Sep 15, 2015 · 1 comment
Labels

Comments

@tecoholic
Copy link

The OpenID Connect spec for client metadata [1] describes the redirect urls using the parameter redirect_uris.

redirect_uris
REQUIRED. Array of Redirection URI values used by the Client. One of these registered Redirection URI values MUST exactly match the redirect_uri parameter value used in each Authorization Request, with the matching performed as described in Section 6.2.1 of RFC3986 - (Simple String Comparison.

But oxD communication protocol for client registration [2] uses redirect_url - a string as the parameter.

This inconsistency between the OIDC spec and oxD implementation should be rectified.

[1] http://openid.net/specs/openid-connect-registration-1_0.html#ClientMetadata
[2] http://ox.gluu.org/doku.php?id=oxd:communication_protocol#register_client

@yuriyz
Copy link
Contributor

yuriyz commented Dec 8, 2015

Fixed in latest master branch. However now we stick to statefull oxd implementation which mean that we have to use register_site operation to get site_id. Please do not use register_client operation anymore unless you have good reason for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants