05-13-2022 04:51 AM - edited 05-13-2022 04:53 AM
Hi,
I have set up the CP successfully.
I see the CP is running on PA redirect IP:6082 with HTTPS.
Is there any way that we can use HTTP only on the CP landing page?
like http://PA_redirect_IP:6082
not https://PA_redirect_IP:6082
We are not using credentials for CP login, our CP just accept and go.
No SSL encryption and protection needed.
So, does PA still support HTTP only captive portal page?
05-13-2022 02:02 PM
Hello,
Just curious as to why? What is the issue with redirection to https?
One thing to remember is that the Palo Alto is a security appliance and tries to do its best to stay that way, hence the https traffic.
Regards,
05-14-2022 02:12 AM
Hi,
Originally, my client was using fortigate. It was using HTTP only for captive portal.
They just want to keep same behaviour after PA replacement. Maybe afraid of the "self-signed cert" error page prompt in some mobile devices (They didn't import and use commercial trusted root cert)?
You know, security guy's comment not always comfort our client. 😄
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
