Copyright © 2010, Juniper Networks, Inc.
Figure 32: Guided Entrance
Service Manager requires additional configuration considerations for the guided entrance
service.
The <# redirectUrlName := "http://" $ serverIp $ ":" $ serverPort #> command in
the service definition—Specifies the HTTP local service to which the subscriber is
redirected after login. See "Guided Entrance Service Definition Example" on page 675
for a sample guided entrance service definition.
NOTE: You must also configure a policy that redirects packets. See Creating an Exception
Rule within a Policy Classifier Group in JunosE Policy Management Configuration Guide
for information on creating redirect policies.
HTTP local server application—Used by the policy in the activated service to direct a
subscriber to a specific Web site when the subscriber logs in. See "Configuring the
HTTP Local Server to Support Guided Entrance" on page 677 for information about the
HTTP local server.
RADIUS Dynamic Request Server and CoA messages—Enables RADIUS to dynamically
activate the new service that the subscriber selects at the Web site. Can also optionally
deactivate the original guided entrance service session that is used when the subscriber
logs in. See "Configuring RADIUS Dynamic-Request Server" on page 231.
Guided Entrance Service Definition Example
This example shows a guided entrance service. Upon login, the subscriber is redirected
to a specific uniform resource locator (URL) at which the subscriber can choose from a
list of available services.
!parameterizes server address and port
<# http(serverIp, serverPort) #>
<# serviceTag := "http-" #>
<# uid := app.servicemanager.getUniqueId #>
<# genericName := "SM-X-" $ serviceTag $ uid #>
<# genericInputName := "SM-I-" $ serviceTag $ uid #>
<# genericOutputName := "SM-O-" $ serviceTag $ uid #>
<# claclName := genericName #>
<# profileName := genericName #>
Chapter 27: Configuring Service Manager
675