<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
0D54z00009hZy1TCASOkta Classic EngineAuthenticationAnswered2023-09-29T22:10:08.000Z2023-09-29T14:16:47.000Z2023-09-29T22:10:08.000Z

User16648134760526564552 (Customer) asked a question.

September 29, 2023 at 2:16 PM
Use same custom domain for 2 applications and display image based on the client id

We have two angular applications both are using different client id to login with the custom authentication flow. Now we are planning to use okta hosted login and for both application we have to use the same custom login. So I have few questions as below.

1) Is there any possibility to user the same custom domain and redirect to the particular application after login?

2) How can I show different logo on the custom domain because when I try to pass client id for the custom domain at that time I am getting 400 bad request error.

3) How we can redirect to particular application after login from the custom domain?

4) If I am opening the okta hosted custom url from the Application1 then Application2 also tries to login then can we use the same session from the Application1?

  • 1 answer
  • 823 views

  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @User16648134760526564552 (Customer)​ 

     

    Thank you for posting on our Community page!

     

    I will answer your questions in order:

    • yes, the application should make an /authorize redirect to log the user into the given app. This will route the user to the Okta hosted login page and, once they complete authentication, they'll be redirected back to the target app via the supplied redirect_uri
    • would need details on the 400 error, but our docs have examples of per-app customizations to the Okta hosted custom sign in widget: https://developer.okta.com/docs/guides/custom-widget/main/#per-application-customization
    • See (1)
    • yes, as long as the user is on the same browser when logging into application 2, when app 2 makes the /authorize requests to the Okta login page, the existing Okta session cookie will be present and it can be used to SSO the user into the second app without them needing to reauthenticate.

     

    I would suggest to open a case with support so they can take a better look at the whole configuration there and guide you step by step.

     

    Thank you for reaching out to our Community and have a great day!

    _____________________________________________________________________________

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    _____________________________________________________________________________

    Headed to Oktane? Here's what you can expect, plus all the Okta tips you may have missed this month

    _____________________________________________________________________________

    Expand Post
This question is closed.
Loading
Use same custom domain for 2 applications and display image based on the client id