0pd0q (0pd0q) asked a question.
Hi all,
We have a few applications integrated with Okta for SSO and they are also deployed on Intune.
We have also configured Networks and setup DSSO.
Wanted to understand behavior around 2 cases :
Will these flows be treated as SP flows (where applicable)?
Thanks much!
Ashwini
HI Ashwini,
You are correct, both scenarios are treated as SP-initiated flows from Okta's perspective.
When accessing a URL or a native app, it is expected that the user would be redirected to Okta for login, when the flow is supported. Mainly, the SP endpoint should support the redirection to Okta for authentication. The concept is more detailed here, in the "Planning for SAML" section:
https://developer.okta.com/docs/concepts/saml/
Additionally, if the SP-initiated flow isn't supported, you can use the app's embed link to trigger the SSO, or if the reverse is true, that is, if the IdP-initated flow is not supported, you can use a Bookmark App as described here:
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Bookmark_App.htm
I hope this helps!
Hi @sebastian.petroi1.5665717802357122E12 (Vendor Management) - We have an environment with multiple forests. There is one way trust on one forest to all other forests. We have installed AD agents in all the domains for Delegated auth and have enabled agentless DSSO
Now, we want to enable Device trust, for which the pre-req is to install IWA agent.
Could you please help me with responses to the following :
Thanks,
Ashwini
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
May Okta Community Buzz
Stay ahead of the curve with Okta for AI Agents, new Okta Learning live sessions and labs, shout-outs, and top trending topics—all aimed at enriching your Okta journey.
HI Ashwini,
You are correct, both scenarios are treated as SP-initiated flows from Okta's perspective.
When accessing a URL or a native app, it is expected that the user would be redirected to Okta for login, when the flow is supported. Mainly, the SP endpoint should support the redirection to Okta for authentication. The concept is more detailed here, in the "Planning for SAML" section:
https://developer.okta.com/docs/concepts/saml/
Additionally, if the SP-initiated flow isn't supported, you can use the app's embed link to trigger the SSO, or if the reverse is true, that is, if the IdP-initated flow is not supported, you can use a Bookmark App as described here:
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Bookmark_App.htm
I hope this helps!