
j8emu (j8emu) asked a question.
Hello,
So we are trying to integrate OKTA SSO on an IOS app (.Net framework/WebAuthenticator).
We've set a custom url scheme in our app and added it to the OKTA config as a callback uri (ourapp:/callback), as per your documentation
https://developer.okta.com/code/ios/quickstart-appauth-swift/
https://developer.okta.com/blog/2023/06/21/net-maui-authentication
My question is simple
Is this considered good practice for production? does it pose a risk?
Thank you

Hi @j8emu (j8emu) , Thank you for reaching out to the Okta Community!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
That being said, I ran this by some of my developer colleagues and they mentioned that
best practice would be the reverse of your domain/anything i.e. com.oktapreview.johnny:/callback .
The only real danger is if you happen to pick some custom schema and some user's device already has an application that also happened to register that exact custom schema.
Also the path can be made more specific since there could be more than one type of callback like: com.mycompany.appname:/signin/callback
I still, strongly recommend reaching out to the dedicated forum for further insights.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--
Help others in the community by liking or hitting Select as Best if this response helped you.