SecureLogin Architecture

SecureLogin is an authentication and single sign-on suite of applications. The application suite consists of an eDirectory database, authentication server, NetWare^® and Windows NT* client authentication plug-ins, and single sign-on modules for most popular applications.

SecureLogin works by keeping a record of user authentication credentials and instructions about how to use these credentials. SecureLogin stores these records in eDirectory. At run time, SecureLogin queries these records and then supplies the correct authentication details for the user.

The SecureLogin script language is a key feature of SecureLogin single sign-on, enabling the product to be compatible with almost all network environments and applications. The script language has the following advantages:

• Allows an administrator to define single sign-on methods for almost any Windows, mainframe, Internet, intranet, Terminal Server or UNIX* application.
• Allows more sophisticated single sign-on to supported applications, including the ability to seamlessly handle several versions of one application.

  This feature is especially important when you upgrade your applications.

All SecureLogin data is stored in one or more database objects residing in eDirectory. SecureLogin's first task on startup is to locate these objects in the eDirectory and cache their contents in memory for later use by the workstation SecureLogin single sign-on agent.

SecureLogin allows you to define which applications are to be enabled for single sign-on. This option gives you

• Full control of which applications can be used for single sign-on
• The ability to update the entire eDirectory database with a new application login script by updating a single object.

These corporate scripts are stored in a Container object rather than individual User objects. For users, the result is a less complex system. For you as the administrator, the improved login mechanisms provide

• A greater level of accountability with increased productivity and security
• A reduced load at the help desk because of significantly fewer password resets

The following figure illustrates SecureLogin architecture.