wghvi (wghvi) asked a question.
Get Domain from CIAM preprod envionment portal for a SwiftUI app
Hi
I'm trying to implement Okta login in a iOS App with SwiftUI
I've found multiple ways to do this:
- Using https://github.com/okta/okta-mobile-swift
- Using Auth0 https://www.youtube.com/watch?v=X3L9GLrWQqI&ab_channel=OktaDev
The problem with the first one is that is not adapted to SwiftUI
So I was trying to use the second option but I can't find the `domain` field in the CIAM preprod envionment portal ( the okta admin portal ).
In the video example they are using the Auth0 portal, but I'm a bit confused, is this different to the Okta portal? Can I get the domain field in the Okta portal?
Am I missing something? Any help is appreciated.
Thanks
Hi @wghvi (wghvi) , 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-custom/developer work).
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
This is probably a better question to ask on the Okta Developer Forum (https://devforum.okta.com) but with said, I think the domain being talked about around the 16:34 time mark of the video for the second option would be your Okta tenant domain or more likely the URI of the Okta Authorization Server you are wanting to use.
Hi Matthew
Thanks for your answer, I will post this question in the okta forum.
To your answer, that's actually the problem, that in the minute 16:34 it shows the domain in the Auth0 portal but I can't find that information in Okta portal.
Thanks both
The domain should be the public URI for your Okta tenant. This is NOT a value that is shown in app config for a Native app in Okta unlike it does in Auth0. If you have a custom domain I would use it otherwise you can use your ....okta.com URI. Don't use your admin URI "-admin.okta.com" as that will not work.