TechLibrary

[+] Expand All

[-] Collapse All

SRC 4.11.x Subscribers and Subscriptions Guide
- Copyright and Trademark Information
- Table of Contents
- List of Figures
- List of Tables
- About the Documentation
- Managing Subscribers and Subscriptions
  - Overview of Subscribers and Subscriptions on a C Series Controller
    - Subscribers Overview
    - Subscriptions Overview
    - Enterprise Subscriber and Subscription Hierarchy
      - Enterprise Subscription Hierarchy
    - Managers Overview
  - Subscriber Logins and Service Activation
    - Login Events and Processes for the SRC Software
    - Residential Subscriber Login and Processes
    - PPP Subscriber Login and Service Activation
    - DHCP Subscriber Login and Service Activation
    - Static IP Subscribers
      - Single PC, IP Address Known
      - Subscriber IP Address Not Known
    - Enterprise Subscriber Login Process
      - Interface Startup
    - Subscriptions and Activations
      - Subscription Activation Interactions
      - Subscription Deactivation Interactions
    - Automatic Activation at Login
      - Enterprise-Specific Remote Session Activation
  - Configuring Subscriber-Related Properties on the SAE (SRC CLI)
  - Classifying Interfaces and Subscribers (SRC CLI)
  - Overview of Plug-Ins Included with the SAE
    - How Internal Plug-Ins Work
      - Plug-In Pool
      - Event Publishers
    - Types of Internal Plug-Ins
    - Assigning DHCP Addresses to Subscribers
    - Creating and Tracking Subscriber Sessions
    - Activating and Tracking Service Sessions
  - Configuring Internal, External, and Synchronization Plug-Ins (SRC CLI)
  - Configuring Accounting and Authentication Plug-Ins (SRC CLI)
    - Creating RADIUS Peers (SRC CLI)
    - Types of Tracking Plug-Ins
      - RADIUS Accounting
    - Configuring Tracking Plug-Ins (SRC CLI)
    - Log Rotation Overview
    - Configuring Log Rotation (SRC CLI)
      - Configuring the FTP Server for Log Rotation (SRC CLI)
      - Configuring the Upload Client for Log Rotation (SRC CLI)
    - Types of Authentication Plug-Ins
    - Configuring Authentication Plug-Ins (SRC CLI)
    - Configuring UDP Ports for RADIUS Plug-Ins (SRC CLI)
    - Defining RADIUS Packets for Flexible RADIUS Plug-Ins
      - Flexible RADIUS Plug-Ins Overview
        Using Default RADIUS Templates
        Naming RADIUS Attribute Instances
        Defining RADIUS Attributes
        Standard RADIUS Attributes
        Juniper Networks VSAs
      - Defining the Values of RADIUS Attributes
      - Configuring a RADIUS Packet Template (SRC CLI)
      - Using Flexible RADIUS Packet Definitions
        Setting Values in Authentication Response Packets
        Selecting IP Address Pools Using DHCP Response Packets
    - Configuring Event Publishers
      - Special Types of Event Publishers
        Configuring Service-Specific Event Publishers
        Configuring Retailer-Specific Event Publishers
        Configuring Virtual Router–Specific Event Publishers
      - Configuring Global and Default Retailer Event Publishers (SRC CLI)
  - Configuring Subscribers and Subscriptions (SRC CLI)
- Redirecting Subscriber Traffic Through Redirect Server
  - Redirecting Subscriber Traffic
    - Traffic Redirection Overview
    - Redirect Server Redundancy
  - Configuring Traffic Redirection (SRC CLI)
- Integrating Junos OS VPNs into an SRC Configuration
  - Adding VPNs from Devices Running Junos OS (SRC CLI)

Download This Guide

Download this guide: SRC 4.11.x Subscribers and Subscriptions Guide

Configuring Redirect Server to Support HTTPS Traffic (SRC CLI)

The SRC software supports to redirect HTTPS IP traffic to a configured destination Web server by using the redirect server. The SRC software intercepts the IP traffic at port 443 and forward it to the port in which the redirect server is configured to listen for HTTPS IP traffic. The redirect server accepts HTTPS IP traffic only from the ports that you configured by using the https-port option at the [edit redirect-server ip-redirect] hierarchy level.

Before you start with setting up a redirection for HTTPS IP traffic, you must create a certificate with the domain name of the URL.

Note: Whenever you open up an HTTPS page, you get a security warning in the browser for the mismatch between common name of the certificate with the domain name of the URL until you add an exception for the certificate in the browser.

Use the following statements to configure the redirect server to support HTTPS IP traffic:

redirect-server https { port port;certificate-identifier certificate-identifier ;protocol (SSLv2 | SSLv23 | SSLv3 | TLSv1);}

redirect-server ipv6-redirect https {port port;certificate-identifier certificate-identifier;protocol (SSLv2 | SSLv23 | SSLv3 | TLSv1);}

Note: We recommend that you do not use the SSLv2 protocol, because it is deprecated.

To configure the redirect server to support HTTPS IPv4 traffic:

In configuration mode, enter the configuration statement that enables the SRC redirect server to redirect HTTPS IPv4 traffic to a configured destination Web server.
[edit]user@host# redirect-server https
Configure the HTTPS port on which the redirect server runs.
[edit redirect-server https]user@host# set port port
Configure the imported Secure Sockets Layer (SSL) certificate. To import the SSL certificate, use the request security import-certificate command.
For information about manually obtaining certificates, see Manually Obtaining Digital Certificates (SRC CLI).
[edit redirect-server https]user@host# certificate-identifier certificate-identifier
Configure the secure connection protocol to be used by the redirect server for IPv4 traffic. The default protocol is TLSv1.
[edit redirect-server https]user@host# protocol (SSLv2 | SSLv23 | SSLv3 | TLSv1)

To configure the redirect server to support HTTPS IPv6 traffic:

In configuration mode, enter the configuration statement that enables the SRC redirect server to redirect HTTPS IPv6 traffic to a configured destination Web server.
[edit]user@host# redirect-server ipv6-redirect https
Configure the HTTPS port on which the redirect server runs.
[edit redirect-server ipv6-redirect https]user@host# set port port
Configure the imported Secure Sockets Layer (SSL) certificate. To import the SSL certificate, use the request security import-certificate command.
For information about manually obtaining certificates, see Manually Obtaining Digital Certificates (SRC CLI).
[edit redirect-server ipv6-redirect https]user@host# certificate-identifier certificate-identifier
Configure the secure connection protocol to be used by the redirect server for IPv6 traffic. The default protocol is TLSv1.
[edit redirect-server ipv6-redirect https]user@host# protocol (SSLv2 | SSLv23 | SSLv3 | TLSv1)

TechLibrary

Download This Guide

Related Documentation

Configuring Redirect Server to Support HTTPS Traffic (SRC CLI)

Related Documentation

Modified: 2017-08-03