Configuring Event Publishers
This topic shows how to configure event publishers. It covers the following tasks:
- Configuring Global and Default Retailer Event Publishers
- Configuring Service-Specific Event Publishers
- Configuring Retailer-Specific Event Publishers
- Configuring Virtual Router-Specific Event Publishers
Configuring Global and Default Retailer Event Publishers
Use the following configuration statements to configure global and default retailer event publishers.
shared sae configuration plug-ins event-publishers {subscriber-authorizationsubscriber-authorization
; default-retailer-authenticationdefault-retailer-authentication
; default-retailer-dhcp-authenticationdefault-retailer-dhcp-authentication
; dhcp-authorizationdhcp-authorization
; service-authorizationservice-authorization
; subscription-authorizationsubscription-authorization
; subscriber-trackingsubscriber-tracking
; service-trackingservice-tracking
; interface-trackinginterface-tracking
; embedded-admin-server-authorizationembedded-admin-server-authorization
;}To configure global and default retailer event publishers:
- From configuration mode, access the event publisher configuration. In this sample procedure, the event publishers are configured in the west-region SAE group.
user@host#edit shared sae group west-region configuration plug-ins event-publishers
- Configure plug-ins that authorize subscriber sessions.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set subscriber-authorization
subscriber-authorization
- Configure plug-ins that authenticate subscribers who are assigned to retailer objects that do not specify an authentication plug-in.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set default-retailer-authentication
default-retailer-authentication
- Configure plug-ins that authenticate DHCP address requests for subscribers who are assigned to retailer objects that do not specify a DHCP authorization plug-in.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set default-retailer-dhcp-authentication
default-retailer-dhcp-authentication
- Configure plug-ins that authorize all DHCP address requests for all DHCP subscribers who log in to a portal.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set dhcp-authorization
dhcp-authorization
- Configure plug-ins that authorize all service sessions.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set service-authorization
service-authorization
- Configure plug-ins that authorize subscribers to change their subscriptions.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set subscription-authorization
subscription-authorization
- Configure plug-ins that collect accounting data for all subscriber sessions.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set subscriber-tracking
subscriber-tracking
- Configure plug-ins that collect accounting data for all service sessions.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set service-tracking
service-tracking
- Configure plug-ins, including network information collector (NIC) SAE plug-in agents, that collect accounting data for all interfaces that the SAE manages.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set interface-tracking
interface-tracking
- Configure plug-ins that authorize administrators to connect to the embedded Web server, which is used to access SAE Web Admin.
[edit shared sae group west-region configuration plug-ins event-publishers]
user@host#
set embedded-admin-server-authorization
embedded-admin-server-authorization
- (Optional) Verify your configuration.
[edit shared sae group west-region configuration plug-ins event-publishers]user@host#show
subscriber-authorization ;default-retailer-authentication ldapAuth;default-retailer-dhcp-authentication ;dhcp-authorization ;service-authorization ;subscription-authorization ;subscriber-tracking fileAcct;service-tracking fileAcct;interface-tracking ;embedded-admin-server-authorization adminLdap;Related Topics
- For information about setting up SAE groups, see SRC-PE Getting Started Guide, Chapter 21, Setting Up an SAE with the SRC CLI.
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.
See SRC-PE Services and Policies Guide, Chapter 1, Managing Services with the SRC CLI.
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.
See Adding Retailers.
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.
For information about configuring virtual routers for JUNOSe routers, see SRC-PE Network Guide, Chapter 5, Using JUNOSe Routers in the SRC Network with the SRC CLI.
For information about configuring virtual routers for JUNOS routing platforms, see SRC-PE Network Guide, Chapter 7, Using JUNOS Routing Platforms in the SRC Network with the SRC CLI.