- play_arrow Juniper Secure Connect Overview
- play_arrow Authentication in Juniper Secure Connect
- SAML Authentication in Juniper Secure Connect
- Local User Authentication Using Pre-shared Key (CLI Procedure)
- External User Authentication (CLI Procedure)
- Example: Configuring LDAP Authentication for Juniper Secure Connect (CLI Procedure)
- Certificate-Based Validation Using EAP-MSCHAPv2 Authentication (CLI Procedure)
- Certificate-Based Validation Using EAP-TLS Authentication (CLI Procedure)
- Local User Authentication Using Pre-shared Key
- External User Authentication Using RADIUS
- Certificate-Based Validation Using EAP-MSCHAPv2 Authentication
- Certificate-Based Validation Using EAP-TLS Authentication
- play_arrow Configure Juniper Secure Connect
- play_arrow Monitor Juniper Secure Connect
- play_arrow Migrate to Juniper Secure Connect
- play_arrow Juniper Secure Connect for Windows
- play_arrow Juniper Secure Connect for macOS
- play_arrow Juniper Secure Connect for Android
- play_arrow Juniper Secure Connect for iOS
Get Started with Juniper Secure Connect
Learn about preparing your environment for Juniper Secure Connect deployment.
Before you deploy Juniper Secure Connect, based on the Figure 1 you must ensure the following:
Include a route in the protected network for the IP address that you assign to the clients, so that it directs traffic to the SRX Series Firewalls.
Implement NAT for the client traffic that enters the protected network.
Ensure that the SRX Series Firewall uses either a signed certificate or a self-signed certificate instead of the default system-generated certificate. You can also use a signed certificate from Let's Encrypt for ACME protocol support.
Read the following topics to get started with the Juniper Secure Connect: