Skip to main content
Solved

NPA Browser Access HTTP vs HTTPS

  • March 13, 2024
  • 3 replies
  • 265 views

Forum|alt.badge.img+5

So i configured a test private application to use HTTP browser access. FYI, the the app is hosted in our AWS environment and uses an auto-generated Amazon certificate. After enabling developer tools in my Chrome browser it clearly shows the session is still using TLS encryption. The only thing visibly different by enabling HTTP vs HTTPS in the private app configuration is it adds 80 to the unique URL name. Everything else appears to be encrypted. Can you explain in more detail what the difference between configuring HTTP and HTTPS?

Best answer by sshiflett

@jschuele

All Browser Access connections will be encrypted between the user’s browser and the Publisher.  The HTTP/HTTPS in the app configuration specifies if the app itself uses HTTP or HTTPS and if HTTPS, whether Netskope should trust self signed certificates.  Browser Access will always use HTTPS for the user session through NPA. 

This topic has been closed for replies.

3 replies

Forum|alt.badge.img+16
  • Netskope Employee
  • 277 replies
  • Answer
  • March 14, 2024

@jschuele

All Browser Access connections will be encrypted between the user’s browser and the Publisher.  The HTTP/HTTPS in the app configuration specifies if the app itself uses HTTP or HTTPS and if HTTPS, whether Netskope should trust self signed certificates.  Browser Access will always use HTTPS for the user session through NPA. 


Rohit_Bhaskar
Netskope Employee
Forum|alt.badge.img+20
  • Netskope Employee
  • 491 replies
  • March 22, 2024

Hi @jschuele ,

Hope you are doing well. I hope the answer shared by @sshiflett  helps you. Feel free to mark a answer as a “Best Answer”

 


Forum|alt.badge.img+5
  • Author
  • New Member III
  • 19 replies
  • March 22, 2024

That answers my question.