9.1 Enabling Applications and Web Sites for Single Sign-On

Novell® SecureLogin has the following features:

Before SecureLogin can enable an application for single sign-on for a particular user, it must learn the user’s application credentials so that SecureLogin can encrypt and store them for future logins, unless it is used in conjunction with Identity Management solutions such as Novell Identity Manager.

When a user starts an application for the first time after the application was enabled for single sign-on, SecureLogin prompts the user for application credentials, and then encrypts and stores them in the directory against the user object. The credentials are passed automatically to the application for subsequent logins.

Automated single sign-on is achieved by using proprietary application definitions. Application definitions are managed in directory environments through SecureLogin management utilities, including the Administrative Management utility, iManager plug-in, and Active Directory MMC plug-in. Locally and in standalone deployments, application definitions are managed in the Personal Management utility or distributed by using the advanced offline signed and encrypted method.

Applications that are enabled for single sign-on are created, modified, and deleted in the Applications pane. You can also create application definitions with SecureLogin wizards. There are a wide range of options in SecureLogin to enable applications. Regardless of the origin of the application definition, when an application is enabled for single sign-on, it is added and maintained in the Applications Properties Table.