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


Loading Subscriptions Based on RADIUS Authorization

You can set up the SAE to load subscriptions based on values that it receives in RADIUS authorization response packets. For this method of loading subscriptions to work, the subscriber must be subscribed to the service.

To use this feature, you set up the RADIUS authorization plug-in to return the setLoadServices attribute, and you specify a regular expression in the SAE property file. When the plug-in returns the setLoadServices attribute, the SAE applies the regular expression to the string in the setLoadServices attribute.

There are two SAE properties that you can use to set the expression:

For example:

SubscriptionParser.regex = ([^;!]*);|([^;!]*)!
SubscriptionParser.auto = 2

A group match corresponds to a regular expression that is enclosed in (). In this example, the regular expression in the subscription parser contains two groups:

  1. A string of characters other than ";" and "!", followed by ";"
  2. A string of characters other than ";" and "!", followed by "!"

The value of 2 in the SubscriptionParser.auto property causes the second group of services—services followed by !—to be activated on login. For example, if the setLoadServices string is video-gold;audio-gold!, it is parsed to video-gold and audio-gold. The audio-gold subscription is activated provided that the subscriber is subscribed to audio-gold services.

NOTE: Persistent service sessions are not parsed. That is, if a subscriber has activated persistent service sessions, then these sessions are activated independent of the RADIUS authorization responses.


Another way to load subscriber services based on RADIUS authorization is to use the serviceBundle vendor-specific attribute (VSA) as input to the subscriber classification script and load different subscriber profiles based on the RADIUS response. Different subscriber profiles subscribe to different services. This approach gives wholesalers a basic tool to outsource service subscriptions to a retailer. The wholesaler and retailer must agree on a RADIUS attribute (for example, serviceBundle) that is provided by the retailer and interpreted by the SAE (that is, the wholesaler).

The subscription parser properties are located in /opt/UMC/sae/etc/dir.template. (See Modifying the SAE Property File.)

SubscriptionParser.regex

SubscriptionParser.auto


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