Special Types of Event Publishers
The SCR CLI lets you configure global and default retailer event publishers. You can also configure service-specific event publishers, retailer-specific event publishers, and virtual router-specific event publishers.
Configuring Service-Specific Event Publishers
In the value-added services definition, you can configure two event publishers for a service:
- Authorization plug-ins—Authenticate subscribers of the service and/or authorize service sessions for this service. These plug-in instances are called before a subscription to this service is activated.
- Tracking plug-ins—Track service sessions of this service. These plug-in instances are called when a service session is started and stopped and during interim updates.
Configuring Retailer-Specific Event Publishers
In the retailer definition, you can configure three event publishers for a retailer:
- Authentication plug-ins—Authenticate subscribers
who log in to the domains of the retailer. These plug-in instances
are called when a subscriber tries to log in to the SAE through the
portal login.
If you do not specify retailer-specific authentication plug-ins, the default retailer authentication plug-ins are called. If you do not specify default retailer authentication plug-ins, subscribers are admitted without authentication.
- Tracking plug-ins—Track sessions of subscribers who log in to the domains of the retailer. These plug-in instances are called after a subscriber session has started and when the session is stopped.
- DHCP authorization plug-ins—Authenticate DHCP address requests for subscribers who log in to the domains of the retailer.
Configuring Virtual Router–Specific Event Publishers
In the virtual router definition, you can configure an interface-tracking plug-in event publisher for a virtual router. These plug-in instances are called when a managed interface is started and stopped. They are called after an interface comes up, when new policies are installed on the interface, and when the interface goes down.
