jtxjh (jtxjh) asked a question.
We have configured both Agentless and On-Prem DSSO in our environment. The routing rule specifies an IP Zone (containing Private IP of the system) and a particular app. When we test app url, DSSO doesn't kick in. However, when we specify Public IP of the system in the IP Zone and retest the app url, DSSO works fine. Can anyone let me know if this is the expected behavior.
Hi @jtxjh (jtxjh) , Thank you for reaching out to the Okta Community!
The Private IP is typically meant for "on network" use. As DSSO requires the use of Okta Cloud services (off network), I would expect only the Public IP to work.
Check what IP is listed under the system logs when the user tries to log in with only that Private IP added to the IP zone that you intend to use for the DSSO.
Seeing as DSSO will not be triggered with that configuration, you will have to "manually" sign in just so you can generate the login event in the logs. Once you've signed in, the logs should show what IP Okta actually sees as being used by that device.
Referenced docs:
https://help.okta.com/en-us/Content/Topics/Security/network/about-ip-zones.htm
https://help.okta.com/en-us/Content/Topics/Reports/Reports_SysLog.htm?cshid=ext_Reports_SysLog
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 it helps!
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 @jtxjh (jtxjh) , Thank you for reaching out to the Okta Community!
The Private IP is typically meant for "on network" use. As DSSO requires the use of Okta Cloud services (off network), I would expect only the Public IP to work.
Check what IP is listed under the system logs when the user tries to log in with only that Private IP added to the IP zone that you intend to use for the DSSO.
Seeing as DSSO will not be triggered with that configuration, you will have to "manually" sign in just so you can generate the login event in the logs. Once you've signed in, the logs should show what IP Okta actually sees as being used by that device.
Referenced docs:
https://help.okta.com/en-us/Content/Topics/Security/network/about-ip-zones.htm
https://help.okta.com/en-us/Content/Topics/Reports/Reports_SysLog.htm?cshid=ext_Reports_SysLog
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 it helps!