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.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.