<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z0000A6ev5WCQQOkta Classic EngineSingle Sign-OnAnswered2024-04-24T17:57:21.000Z2024-04-23T19:33:35.000Z2024-04-24T17:57:21.000Z

User1713199805234524992 (Customer) asked a question.

April 23, 2024 at 7:33 PM
Is sign on url guaranteed to stay unchanged for an org?

I was setting WhyLabs SCIM Provisioning with Okta: https://docs.whylabs.ai/docs/whylabs-scim-okta. (SCIM 2.0 Test App (Header Auth))

After setup completion, I (admin user) can access to the sign on url on Okta SCIM application under "Sign on" section.

 

Is the sign on url guaranteed to stay unchanged for an org? 

And I'm trying to understand the "Sign on URL". Let's say we have a org, and there are multiple users under this org, like admin, and other users. So all types of the users can use the same sign on url to enter user's credential and sign in into the 3rd party app (WhyLabs)?

Thank you.

  • 7 answers
  • 282 views

  • Mihai N. - Okta (Okta, Inc.)

    Hi @User1713199805234524992 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    I can confirm that the URL is not variable or dynamic. It is automatically generated for that particular app instance once, when you created it in Okta and it gives it the unique identifier (not to be confused with appID ) so that it can be used for SSO purposes. It will remain unchanged until you delete the app.

     

     

    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.

    Expand Post
    Selected as Best

  • Mihai N. - Okta (Okta, Inc.)

    Hi @User1713199805234524992 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    I can confirm that the URL is not variable or dynamic. It is automatically generated for that particular app instance once, when you created it in Okta and it gives it the unique identifier (not to be confused with appID ) so that it can be used for SSO purposes. It will remain unchanged until you delete the app.

     

     

    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.

    Expand Post
    Selected as Best

  • User1713199805234524992 (Customer)

    Hi @Mihai N. - Okta (Okta, Inc.)​ , thank you for your confirmation. I'm also trying to understand the purpose of the sign on url. So after I go to this sign on url, will the webpage ask me to enter my credentials to the 3P app (enter username and password)? If so, after I entered my credential and click "Sign in", Okta will do authentication and if authentication passed, I will be redirected to the 3P app interface or I will be redirected to some other webpage? Thank you!

    Expand Post

    • Mihai N. - Okta (Okta, Inc.)

      That particular URL under the "Sign On" tab of the app in the Okta admin dashboard is leveraged as part of the configuration for your SAML SSO (metadata) configuration in your downstream app. The users would not be leveraging that directly.

      If needed, the users would leverage the URL mentioned under the "General" tab > "App Embed Link".

       

      Regards.

      --

      Help others in the community by liking or hitting Select as Best if this response helped you.

      Expand Post

  • User1713199805234524992 (Customer)

    Hi @Mihai N. - Okta (Okta, Inc.)​ , I see, thanks for sharing. I located that url called "App Embed Link" right? So could you confirm the link behavior in user experience perspective? For example, if I have access to this url link, I can go to this url, and then the webpage will ask me to enter my credential, and if my credential passed the authentication, I will be directly brought to the 3rd party app interface?

    I'm trying to find the url that can be used for this purpose mentioned above which basically redirect user to the 3rd party app interface. Thank you.

     

    Expand Post

  • User1713199805234524992 (Customer)

    Hi @Mihai N. - Okta (Okta, Inc.)​ , I tried go to the embed link url, it automatically redirect me to the okta product page, not the 3rd party app interface. Can you suggest here which url I can use to be redirected to the 3P app interface?

    • Mihai N. - Okta (Okta, Inc.)

      I've reviewed the rest of the documentation on the WhyLabs side and it does not mention any SSO capabilities.

      This implementation is strictly for Provisioning purposes. To push or import users/groups to or from the WhyLabs side, not for authentication purposes.

      I recommend reaching out to them to confirm if they support an SSO configuration.

       

      Regards.

      --

      Help others in the community by liking or hitting Select as Best if this response helped you.

       

      Expand Post
This question is closed.
Loading
Is sign on url guaranteed to stay unchanged for an org?