Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Login Events and Processes for the SRC Software

 

Login interactions between the components differ according to the type of subscriber. Topics include:

Login Events and Processes Overview

Because of the different ways that residential and enterprise subscribers connect, the login interactions between the components differ according to the type of subscriber. Because residential customers can connect by Point-to-Point Protocol (PPP), Dynamic Host Configuration Protocol (DHCP), or static IP addresses, the interactions between the SRC components differ according to the method of connection that a residential subscriber uses. However, there is only one type of login interaction—the subscriber interface login interaction—for enterprise subscribers.

Logins to plug-ins can occur during the login to the service activation engine (SAE) or during the activation of subscriptions. For these processes, many of the interactions between the SRC components are the same regardless of the type of subscriber and the type of connection.

Login Events

Each login process begins with a login event, as described in Table 5.

Table 5: Login Events

Login Event

Event Is Triggered When

SAE Response

AUTHINTF

An interface responds to authentication, such as authentication for a PPP session. (Supported on JunosE routers.)

Invokes subscriber classification script,

creates subscriber session.

INTF

An interface comes up and the interface classifier script determines that the SAE should manage the interface, unless the interface comes up as a result of an authenticated PPP session. (Supported on device running Junos OS and JunosE routers.)

Invokes subscriber classification script,

creates subscriber session.

ADDR

A subscriber obtains an unauthenticated IP address from the router through DHCP. (Supported on JunosE routers.)

Invokes subscriber classification script,

creates subscriber session.

AUTHADDR

A subscriber obtains an authenticated IP address from the router through DHCP. (Supported on JunosE routers.)

Invokes subscriber classification script,

creates subscriber session.

PORTAL

The portal API is invoked by a JSP webpage to log in a subscriber. (Supported on device running Junos OS and JunosE routers.)

Authenticate subscriber,

invokes subscriber classification script,

creates subscriber session.

ASSIGNEDIP

An application accesses a subscriber object for an assigned IP subscriber that is not currently loaded into memory.

Invoke subscriber classification script,

creates subscriber session.

Summary of the Login Process

The SAE login process is summarized in the steps below. If any of the steps fail, the login process stops, and no subscriber session is created.

  1. A login event occurs (see Login Events) and triggers the login process.

  2. In case of a portal login, the SAE invokes the authentication plug-ins to authenticate the request.

  3. The SAE invokes the subscriber classification script and provides to the script details about the login event (for example, interface name, subscriber IP address if available, login name if available, and login event type).

  4. The script sends an LDAP query that uniquely identifies a subscriber entry in the directory to the SAE.

  5. The SAE loads the subscriber entry from the directory and uses the entry to create a subscriber session in memory.

  6. The SAE queries all configured authorization plug-ins about whether it should allow the login.

  7. The SAE completes the login process by activating the subscriber’s activate-on-login subscriptions.