https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177775#M32557 <P>Chris definitely brings up good points in his response.</P> Mon, 10 Apr 2023 13:12:38 GMT the_rock 2023-04-10T13:12:38Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177755#M32553 <P>Browser based authentication URL showing not secure for few users.</P><P>like ex: its showing <A href="http://192.168.1.1" target="_blank">http://192.168.1.1</A>&nbsp;but once we go for advanced tab it redirect to login page</P><P>its happening for few internal users only not for all users</P><P>Can anyone give me suggestion for the issue</P><P>&nbsp;</P> Mon, 10 Apr 2023 08:01:22 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177755#M32553 Manivardhan 2023-04-10T08:01:22Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177764#M32554 <P>Can you please describe more about the certificate / trust elements deployed in the environment as relevant to the above?</P> <P>Does it happen only for BYOD or mobile devices?</P> Mon, 10 Apr 2023 09:22:01 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177764#M32554 Chris_Atkinson 2023-04-10T09:22:01Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177765#M32555 <P>yes, its happing in mobile devices</P> Mon, 10 Apr 2023 10:21:59 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177765#M32555 Manivardhan 2023-04-10T10:21:59Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177766#M32556 <P>1.) Is the URL a HTTP or HTTPS address? (Browsers such as Chrome will complain about this.)</P> <P>2.) Any certificates involved must be signed by a CA that the Endpoint trusts otherwise warnings will result. See also:</P> <P><A href="https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_IdentityAwareness_AdminGuide/Topics-IDAG/Server-Certificates.htm?tocpath=Advanced%20Browser-Based%20Authentication%20Configuration%7CServer%20Certificates%7C_____0#Server_Certificates" target="_blank" rel="noopener">https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_IdentityAwareness_AdminGuide/Topics-IDAG/Server-Certificates.htm?tocpath=Advanced%20Browser-Based%20Authentication%20Configuration%7CServer%20Certificates%7C_____0#Server_Certificates</A></P> Mon, 10 Apr 2023 10:43:27 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177766#M32556 Chris_Atkinson 2023-04-10T10:43:27Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177775#M32557 <P>Chris definitely brings up good points in his response.</P> Mon, 10 Apr 2023 13:12:38 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Browser-based-authentication-URL-showing-not-secure/m-p/177775#M32557 the_rock 2023-04-10T13:12:38Z