I am looking to embed the okta sign in widget on a web page. Instead of having the separate sign in page we would like to embed this page in the actual application in left or right pane and have the similar execution as it does with standalone page.
@alisaduncan Thanks for your response but i wanted to also check that can i embed the okta hosted sign in widget to app instead of having separate page. I am not looking to have create an embedded sign in page.
@jmussman Thanks for replying i picked the below piece of code and tried launching the widget after filling issuer,redirect uri, client id & base url but it does not seem to load anything there are no errors in console and network as well:
Also i am having an OIDC web application and would want to use the sign in widget embedded in the application instead of having a separate sign in page as okta hosed sign in page
Before we go to deep, may I ask why? Using the widget hosted locally instead of at Okta generally eliminates single sign-on across multiple applications (the user doesn’t get a session at Okta). You are pretty much using Okta as a directory service, like LDAP. That doesn’t mean you don’t have a good reason, but often setting up the background image, logos, and using a custom domain name while letting Okta host the widget lets the user think they haven’t left your environment, but then they get a session cookie and SSO works.
Actually we are looking to set the sign in screen with our home screen instead of redirecting the user to different page and increase the usability of Home page from Anonymous user perspective. It is basically we are trying to redesign our application and would want to include the sign in page in home screen for users who have not logged in.