Issues when adding several redirect_uri for an OIDC client's entry
See original GitHub issueEnvironment: gluu-server-3.1.4-RC6, CentOS7
Steps to reproduce;
- Log in to web UI
- Move to “OpenID Connect -> Clients”
- Create a new client entry with minimal set of required properties; use “pairwise” for “Subject Type” and specify only one redirect login uri
- Try to add an additional redirect uri with the same hostname part as the 1st one has (that step should fail, see below for details)
- Supply a valid “Sector Identifier URI” which returns a JSON file containing both of the redirect uris used in this test (use a uri pointing to a remote web server), and click the “Update” button
- Try to add 2nd redirect uri again
Results:
- At step 4) an error message is displayed reading “A sector identifier must be defined first” and Java error trace is registered in
oxtrust.log
(full text is here):
2018-09-24 16:44:07,520 ERROR [qtp1094834071-14] [org.gluu.oxtrust.ldap.service.SectorIdentifierService] (SectorIdentifierService.java:90) - Failed to find sector identifier by oxId sector-uris.json
org.gluu.site.ldap.persistence.exception.EntryPersistenceException: Failed to find entry: oxId=sector-uris.json,ou=sector_identifiers,o=@!E8DE.7456.204B.BE5E!0001!25AB.4068,o=gluu
at org.gluu.site.ldap.persistence.LdapEntryManager.find(LdapEntryManager.java:306) ~[oxcore-ldap-3.1.4-SNAPSHOT.jar:?]
at org.gluu.site.ldap.persistence.AbstractEntryManager.find(AbstractEntryManager.java:444) ~[oxcore-ldap-3.1.4-SNAPSHOT.jar:?]
at org.gluu.site.ldap.persistence.AbstractEntryManager.find(AbstractEntryManager.java:381) ~[oxcore-ldap-3.1.4-SNAPSHOT.jar:?]
- At step 6) the same message and same log record are seen again, despite of the fact “Sector Identifier URI” is defined now
Expected results:
- According to the spec, sector identifier uri only becomes mandatory when several redirect uris are used and their hostname parts are different. Thus the fact a 2nd uri couldn’t been added at step 4) doesn’t seem right
- Even when a correct sector identifier uri is added as web UI requests, it’s still not possible to add a 2nd redirect uri, thus it doesn’t seem this web UI control functions properly at all
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Redirect URI (reply URL) restrictions - Microsoft Entra
A description of the restrictions and limitations on redirect URI (reply URL) format enforced by the Microsoft identity platform.
Read more >Add a redirect URI to a login client - Akamai TechDocs
Two things to keep in mind when adding a redirect URI to an OIDC client. First, make sure you specify all the properties...
Read more >redirect_uri_mismatch error occurs when using AM (All ...
Configured AM as an OAuth Authorization Server (with or without the OpenID Connect authentication layer) to make AM an OAuth2 / OpenID provider....
Read more >Insufficient Redirect URI validation: The risk of allowing to ...
Insufficient Redirect URI validation: The risk of allowing to dynamically add arbitrary query parameters and fragments to the redirect_uri.
Read more >Retrieving the authentication/redirect URI and Client ID to use ...
Since the June release, K2 Cloud has started using Open ID Connect (OIDC) to authenticate and authorize users. With this change, the OAuth ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@aliaksander-samuseu i’m the one who implement that restriction.
sector identifier uri only becomes mandatory when several redirect uris are used and their hostname parts are different: This wasn’t not mentioned in that task.
Here is the link https://github.com/GluuFederation/oxTrust/issues/966.
@aliaksander-samuseu i think it’s okay now.