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

## 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 Table 5) 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.

#### Related Topics

- Overview of Login Events and Processes
- Residential Subscriber Login and Processes
- Login Events
- Enterprise Subscriber Login Process
- Adding Residential Subscribers (SRC CLI)

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