You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by a partner in ticket 11012
When adding a deep link kind of uri (example: myapp://com.callback) as redirect_uri for an OIDC client, oxTrust will respond with "The url is malformed" error pop up and will refuse to add it. The code checking for it seems to be embedded in the page itself.
Steps To Reproduce
Log in as admin user
Move to OpenID Connect > Clients
Create a client entry, or use an existing one; open it for editing and try to add a uri above as redirect_uri (the partner used uri like this com.okta.dev-55232784:/callback)
Expected behavior
oxTrust must allow addition of deep linking redirect_uri-s at least for the "Native" type of client. Though it may be needed to support it for "Web" as well (need to be assessed by somebody with sufficient expertise in mobile app development)
Actual behavior
The uri is rejected with "The url is malformed" error pop up
The text was updated successfully, but these errors were encountered:
Any valid URI should be allowed. See https://www.rfc-editor.org/rfc/rfc6749#section-3.1.2
Ignore "should use tls"... if the client doesn't want to use tls, that's up to it. Also, for non web protocols, the messaging may be encrypted anyway.
Description
Reported by a partner in ticket 11012
When adding a deep link kind of uri (example:
myapp://com.callback
) as redirect_uri for an OIDC client, oxTrust will respond with "The url is malformed" error pop up and will refuse to add it. The code checking for it seems to be embedded in the page itself.Steps To Reproduce
OpenID Connect
>Clients
redirect_uri
(the partner used uri like thiscom.okta.dev-55232784:/callback
)Expected behavior
oxTrust must allow addition of deep linking redirect_uri-s at least for the "Native" type of client. Though it may be needed to support it for "Web" as well (need to be assessed by somebody with sufficient expertise in mobile app development)
Actual behavior
The uri is rejected with "The url is malformed" error pop up
The text was updated successfully, but these errors were encountered: