A
- access lines 1
- accesses
- configuring subscriptions
- accounting
- anonymous subscriber
- attributes
- authenticated subscriber
- authentication plug-ins
- authorization plug-ins
B
C
- captive portal
- classification scripts
- conditions 1
- configuring
- descriptions
- DHCP classification, C Series Controller
- interface classification, C Series Controller
- structure
- subscriber classification, C Series Controller
- target, C Series Controller
- component interactions
- conventions
- COPS (Common Open Policy Service)
- custom RADIUS accounting plug-ins 1
- configuring
- custom RADIUS authentication plug-ins 1
- configuring
- customer support 1
D
- default retailer authentication plug-ins
- configuring
- default retailer DHCP authentication plug-ins
- configuring
- denial-of-service attacks
- DHCP (Dynamic Host Configuration Protocol)
- address assignment
- classification scripts. See classification scripts
- options
- profiles
- subscribers
- documentation
E
- enterprise
- enterprise subscribers 1
- adding
- enterprise subscribers, login process
- event publishers
- configuring
- default retailer authentication, configuring
- default retailer DHCP authentication, configuring
- description
- retailer-specific
- service-specific
- virtual router-specific
- external plug-ins
- configuring
F
- file upload settings for log rotation
- configuring
- flat file accounting plug-ins 1
- flexible RADIUS accounting plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- flexible RADIUS authentication plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- setting responses
- FTP server for log rotation
G
- general properties
- configuring
H
- HTTP proxy 1, 2
- HTTPS traffic
I
- interface classification scripts. See classification scripts
- interim accounting, configuring on SAE
- internal plug-ins
- configuring
L
- LDAP authentication plug-in 1
- configuring
- limiting subscribers plug-in 1
- configuring
- log rotation
- overview
- logging
- login events, description
- login process
- login registration
- configuring
- logout process, residential
M
- managers
- manuals
N
- NAT (Network Address Translation)
- notice icons
P
- plug-ins
- activating service sessions
- authentication
- authorization
- basic RADIUS accounting 1
- basic RADIUS authentication 1
- creating subscriber sessions
- custom RADIUS accounting 1
- custom RADIUS authentication 1
- defining RADIUS packets
- DHCP address assignment
- event publishers. See event publishers
- external
- flat file accounting 1
- flexible RADIUS accounting 1
- flexible RADIUS authentication 1
- internal 1
- LDAP authentication 1
- limiting subscribers 1
- state synchronization
- tracking
- policy groups
- policy management
- PPP subscribers
- prevention, use of unauthorized resources
- protocols
- proxy HTTP 1, 2
- proxy request management
- public addresses, VPNs
Q
R
- RADIUS accounting
- RADIUS attributes
- defining in RADIUS plug-ins
- examples, defining in RADIUS plug-ins
- RADIUS client library, custom RADIUS plug-ins
- RADIUS packets, customizing in plug-ins
- RADIUS peers
- configuring in plug-ins
- RADIUS plug-ins 1, See also plug-ins
- redirect server
- assessing load
- configuration statements
- configuring
- configuring DNS server for
- configuring HTTP proxy support
- configuring redundant
- directory connection
- failover
- file extensions
- logging
- number of requests
- protection against denial-of-service attacks
- redundancy 1, 2, 3
- static route to router
- traffic definition
- verifying
- redundancy
- residential subscribers 1
- adding
- login process. See login process
- retailers
- subscribers 1
- router subscribers 1
- adding
- routing instances
- routing scheme
S
- SAE (service activation engine)
- classification scripts. See classification scripts
- login events
- login process. See login process
- SAE (service activation engine), configuring
- service activation engine. See SAE
- service sessions
- sites 1, 2, 3
- subscriber 1
- state synchronization plug-in interface
- configuring
- static IP subscribers, login process
- static routing
- subscriber classification scripts. See classification scripts
- subscriber folders 1
- adding
- subscriber sessions
- subscribers
- 3gpp attributes (Gx router driver)
- adding
- enterprise 1
- inheriting properties
- inheriting subscriptions
- residential 1
- retailer 1
- router 1
- sessions
- sites 1
- types
- subscriptions 1
- access, configuring
- an orderly deactivation, activation order, specifying
- configuring
- multiple per subscriber
- support, technical See technical support
T
- targets. See classification scripts
- technical support
- text conventions defined
- tracking plug-ins 1
- configuring
U
- UDP ports
- User Datagram Protocol. See UDP
V
- validating
- virtual private networks. See VPNs
- VPNs (virtual private networks)
- adding
- configuration requirements
- configuration statements
- extranet clients, modifying
- invalid subscriptions
- modifying
- routing schemes
- using NAT
- validating
Download This Guide
Related Documentation
- Configuration Statements for the Redirect Server (SRC CLI)
- Defining Traffic to Transmit to the Redirect Server (SRC CLI)
- Commands to Manage Digital Certificates
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:
![]() | 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)
Related Documentation
- Configuration Statements for the Redirect Server (SRC CLI)
- Defining Traffic to Transmit to the Redirect Server (SRC CLI)
- Commands to Manage Digital Certificates