Unable to configure custom url in oauth clients for mobile apps

Sai Kishan
Sai Kishan E Member
edited October 2 in Q&A #1

Hi Team,

The current Redirect URLs section under the admin center seems to support only the urls having http / https.

But for the development of mobile apps, we might need to configure the custom url as shown below. This currently doesn't seem to be supported.

Tagged:

Comments

  • Roger K
    Roger K E Community Moderator
    edited July 24 #2

    @Sai Kishan It is true that we do not currently support custom url schemes such as the one you provide above.

    However, using App-claimed url redirection you should be able to configure the mobile device to redirect to where you want to go. Android and iOS support this feature and is the preferred approach according to this Oauth article.

    https://www.oauth.com/oauth2-servers/redirect-uris/redirect-uris-native-apps/

  • Sai Kishan
    Sai Kishan E Member
    edited July 25 #3

    Hi @Roger K

    Thanks for pointing us to the helpful resource. But for iOS, the https url redirected to Safari; so we had to do some customizations in terms of using WKWebView.

    However, seems OTDS is currently supporting the custom urls through their APIs i.e. using POST /oauthclients (Ref: https://developer.opentext.com/ce/products/opentext-directory-services/apis/otds-241-rest-api)

    I feel the restriction from the leading app (Admin Center) could be relaxed going forward.

  • Hi,

    It looks like the current Redirect URLs section in the admin center only supports URLs with http/https. However, when developing mobile apps, we often need to configure custom URLs (e.g., app-specific schemes), which doesn't seem to be supported at the moment.

    Is there any workaround or plan to support custom URL schemes?

  • Roger K
    Roger K E Community Moderator

    @James Browsn The workaround/preferred production solution is described in the thread above. There are no immediate plans to support custom URL schemes … its in the backlog though.

  • Oh, sorry! Thanks for highlighting that.