The Novell SecureLogin has predefined applications for single sign-on access to a wide range of commercially available applications.
Novell SecureLogin detects applications for which a predefined application exists. For example, if Novell SecureLogin detects a SAP* dialog box, then it prompts the user to allow the Novell SecureLogin to enable single sign-on for the application.
NOTE:Predefined applications for some commonly used applications are incorporated with the Novell SecureLogin, and with each new version, more applications are developed and made available to the customers. For detailed information on the predefined applications, see
Using a Predefined Application to Enable a Web Application in the Novell SecureLogin 6.1 Administration Guide.
The Novell SecureLogin provides wizards and applications to facilitate single sign-on to almost any new or proprietary application if a predefined application is not available. This helps the users or a Novell Consultant to build an application definition for almost any proprietary application or an upgrade. For more information, see Section 3.0, The Novell SecureLogin Components.
Novell SecureLogin also supports enabling the single sign-on for standard terminal emulator applications.
Users can enable single sign-on for terminal emulators by using the terminal launcher tool.
Novell SecureLogin has additional tools such as, Window Finder and LoginWatch, which help the user to enable single sign-on for even the most difficult applications. For details, refer to the Novell SecureLogin 6.1 SP1 Application Definition Guide.
Novell SecureLogin stores the login information requirements for applications including the following:
Credentials, but not limited to:
Responses to dialog boxes, messages, and window events such as:
Before Novell SecureLogin can enable an application for single sign-on for a particular user, it must learn a user’s application credentials so that it 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 it is enabled for single sign-on, the Novell SecureLogin prompts the user for application credentials, 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 the proprietary application definitions. The application definitions are managed in directory environments through the Novell SecureLogin administrative management utilities. In local and standalone deployments, the application definitions are managed in the Personal Management utility or distributed by using the advanced offline signed and encrypted method.
The single sign-on applications are created, modified, and deleted in the Applications pane. Users can also create application definitions with the Novell SecureLogin Wizard. There a wide range of options in the Novell 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 theproperties table.
For detailed procedures about enabling applications and Web sites for single sign-on, see
Enabling Applications and Web Sites in the Novell SecureLogin 6.1 Administration Guide.