[Contents] [Prev] [Next] [Index] [Report an Error]

# Before You Install and Configure the Sample Residential Portal

Before you install and configure the sample residential portal:

- Decide which behavior model the portal will use:
  - Equipment registration behavior—The equipment registration example demonstrates an application that provides an association between a subscriber and the equipment being used to make the DHCP connection. This type of association is used in many cable environments.
  - ISP service behavior—The ISP service example demonstrates an application that provides a means for subscribers to directly log in to a subscriber session for their ISP. The ISP service behavior is well suited for any environment in which subscribers connect directly to their ISP.
  - Cable behavior—The cable behavior is provided for a PCMM environment in which an application creates a subscriber session.
- (Optional) Set up subscriber authentication through RADIUS at portal login.
- (Optional) Customize how the sample residential portal handles unrecognized IP subscribers.

## Configuring Equipment Registration and ISP Service Behaviors

The equipment registration and ISP portal behaviors use a RADIUS server for authentication and authorization. The Juniper Networks database and the add-on packages for other supported directories include sample data to authenticate portal logins. RADIUS servers can be configured to use these directories.

The version of Steel-Belted RADIUS in the SRC software distribution is preconfigured to use the SRC sample data to authenticate the domains for the sample residential portal. In the Steel-Belted RADIUS configuration, identify the host on which the directory is running if the host (if it is not localhost).

## Configuring Cable Behavior

For a PCMM environment, you can create an application to create a subscriber session by either:

- Using the event API to integrate an IP address manager such as a DHCP server or a RADIUS server.
- Having the application provide the IP address, the associated interface name, and virtual router name for the subscriber making the request. Typically, the IP address is used to identify the associated virtual router.

If the application provides the subscriber IP address and associated information, you can configure the portal application to locate the SAE that manages the subscriber session by configuring one of the following:

- Network information collector (NIC)
  - NIC host that resolves a subscriber IP address to name of the virtual router managing the IP address and an SAE interoperable object reference (IOR)
  - NIC proxy for the application to communicate with the NIC host
- A local feature locator in the properties for the residential portal. See WEB-INF/portalBehavior.properties .

## Authenticating Subscribers Through RADIUS

If you use RADIUS to manage subscriber data, you can use RADIUS to authentication subscribers when they log in to a residential portal. You configure RADIUS authentication plug-ins to provide RADIUS authentication or authorization. In the configuration for the plug-in, you specify how the SAE handles RADIUS attributes received from the RADIUS server.

Because the SAE rather than a JUNOSe router receives the authentication response, you can specify that the response include attributes other than serviceBundle and class, and you can specify more than value for the RADIUS class attribute.

To authenticate subscribers through RADIUS at portal login:

1. Create a RADIUS authorization plug-in to authenticate subscriber sessions.
2. Configure the RADIUS authorization plug-in to specify:
   - The RADIUS attributes to be set in an authorization response
   - The action to be taken in response to the attribute values received

For example, you could create a RADIUS authorization plug-in to:

- Authenticate a PPP subscriber session on a JUNOSe router
- Specify the setLoadServices value for the serviceBundle attribute

  By default, the flexible RADIUS authentication plug-in defines this attribute as:

  `
  RadiusPacket.stdAuth.userresp.vendor-specific.Juniper.Service-Bundle = setLoadServices
  `

For more information about RADIUS authentication plug-ins, see SRC PE Subscribers and Subscriptions Guide.

## Customizing How the Sample Residential Portal Handles Unrecognized IP Subscribers

By default, the sample residential portal sends unrecognized IP subscribers to a login page rather than to an error page.

To customize how unrecognized IP subscribers are handled:

- Edit the struts-config.xml file.

[Contents] [Prev] [Next] [Index] [Report an Error]