RayS.21978 (Customer) asked a question.
I’m tasked to bypass Okta authentication on our company Intranet site that is also an Okta app. Originally, the task was to have all users within the local LAN have this Intranet site as their Google Chrome default web page, and this was easily accomplished by a group policy object in Active Directory. In addition, there is an existing Okta exclusion rule for all users within the local LAN to bypass Okta authentication which works just fine until they launch their Chrome browser. The moment they launch their Chrome browser they are prompted to authenticate through Okta, and this is on the company’s local LAN. If you have any insight and/or experience with this, I’d appreciate any assistance on how to resolve this.
Hello @RayS.21978 (Customer) Thank you for posting on our Community page!
This depends on the application, if once SAML has been enabled it still allows other forms of authentication or just though the IDP. There are applications that do not allow it and some allow username and password after SAML has been setup. On the Okta side there is no setting to bypass the authentication.
Or you can setup IWA fro your company and then the authentication will happen automatically if a user is on corporate network and they try to authenticate on an application that is setup through Okta.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.