Configuring Event Publishers
This section 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
You can use SDX Configuration Editor to configure global and default retailer event publishers. To do so:
- Access the plug-in configuration as described in Accessing the Plug-In Configuration.
![]()
- In the Plug-In Event Publishers area, enter a comma-separated list of plug-in instances in each event publisher field that you want to configure.
Global User Authorization Plug-ins
- Authorize all subscriber sessions. These plug-in instances are called after a subscriber profile is loaded but before a subscriber session is started. The SAE calls these plug-ins for each subscriber who logs in to a portal.
- These plug-in instances cannot perform authentication, because passwords are not available at this point in the login process. Therefore, if you specify plug-in instances that perform authentication, login requests will fail.
- Value—Comma-separated list of plug-in instances
- Default—No value
- Property name—User.auth.plugins
Default Retailer Authentication Plug-ins
- Authenticate subscribers who are assigned to retailer objects that do not specify an authentication plug-in. These plug-ins are called when a subscriber logs in to the domain. The authentication process for portal (Web) logins maps the supplied domain name to a retailer object.
- If you do not specify default retailer authentication plug-ins or retailer-specific plug-ins, subscribers are admitted without authentication.
- Value—Comma-separated list of plug-in instances
- Default—ldapAuth
- Property name—Retailer.auth.plugins
Default Retailer DHCP Authentication Plug-ins
- Authenticate DHCP address requests for subscribers who are assigned to retailer objects that do not specify a DHCP authorization plug-in. These plug-ins are called when the SAE receives a DHCP discover request from a client that has its username and password cached in the SAE. The username and password can either be cached persistently in the directory or temporarily in memory during a switch from an unauthenticated to an authenticated address.
- Value—Comma-separated list of plug-in instances
- Default—No value
- Property name—Retailer.dhcpauth.plugins
Global DHCP Authorization Plug-ins
- Authorize all DHCP address requests for all DHCP subscribers who log in to a portal. These plug-in instances are called for both authenticated and unauthenticated address requests.
- Value—Comma-separated list of plug-in instances
- Default—No value
- Property name—Dhcp.auth.plugins
Global Service Authorization Plug-ins
- Authorize all service sessions. These plug-ins are called before a service session is started, and are called for every service session started by any SAE subscriber.
- Value—Comma-separated list of plug-in instances
- Default—No value
- Property name—Service.auth.plugins
Global Subscription Authorization Plug-ins
- Authorize subscribers to change their subscriptions. These plug-ins are called when a subscriber tries to modify, subscribe to, or unsubscribe from a subscription.
- Value—Comma-separated list of plug-in instances
- Default—No value
- Property name—Subscription.auth.plugins
Global User Tracking Plug-ins
- Track all subscriber sessions. These plug-in instances are called for every subscriber session that is started and stopped. They are called after a subscriber session has started and when the session is stopped.
- Value—Comma-separated list of plug-in instances
- Default—fileAcct
- Property name—User.tracking.plugins
Global Service Tracking Plug-ins
- Track all service sessions. These plug-in instances are called for every service session that is started and stopped. They are called after a service session starts, when the service session stops, and during interim updates.
- Value—Comma-separated list of plug-in instances
- Default—fileAcct
- Property name—Service.tracking.plugins
Global Interface Tracking Plug-ins
- Track all interfaces that the SAE manages. You can set up the publisher to send interface tracking events to plug-in instances or to a network information collector (NIC) SAE plug-in agent. These plug-in instances and/or NIC SAE plug-in agents are called for every managed interface that 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.
- Value—Comma-separated list of plug-in instances or NIC SAE plug-in agents
- Default—No value
- Property name—Interface.tracking.plugins
Embedded AdminServer Authorization Plug-ins
- Authorize administrators to connect to the embedded Web server, which is used to access SAE Web Admin.
- Value—Comma-separated list of plug-in instances
- Default—adminLdap
- Property name—AdminServer.realm.auth.plugins
Configuring Service-Specific Event Publishers
In the value-added services definition in SDX Admin, 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.
You configure these event publishers in the SSP Services window in SDX Admin. See SRC-PE Services and Policies Guide, Chapter 2, Managing Services on a Solaris Platform.
Configuring Retailer-Specific Event Publishers
In the retailer definition in SDX Admin, 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.
You configure these event publishers in the Retailer pane in SDX Admin. See Adding Retailers.
Configuring Virtual Router-Specific Event Publishers
In the virtual router definition in SDX Admin, 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.
You configure this event publisher in the VirtualRouter pane in SDX Admin. For information about configuring virtual routers for JUNOSe routers, see SRC-PE Network Guide, Chapter 6, Using JUNOSe Routers in the SRC Network with a Solaris Platform. For information about configuring virtual routers for JUNOS routing platforms, see SRC-PE Network Guide, Chapter 8, Using JUNOS Routing Platforms in the SRC Network with a Solaris Platform.