4.0 Enabling Applications and Web Sites for SSO

SecureLogin:

Has predefined applications for SSO access to a wide range of commercially available applications.
Detects applications for which a predefined application exists. For example, if SecureLogin detects an SAP logon dialog box, then SecureLogin displays a prompt providing the user with the option to allow SecureLogin to automatically SSO the application.

NOTE:Predefined applications for commonly used applications are provided with the SecureLogin application, and with each new version, more are developed and made available to Novell customers.
Provides wizards and application definitions to facilitate SSO to almost any new or proprietary application if a predefined application is not available. This helps you or Novell Technical Services to build an application definition for almost any proprietary application or upgrade. For more information, see Section 2.0, SecureLogin Components.
Supports SSO-enabling of most standard terminal emulator applications.

NOTE:You can SSO-enable terminal emulators using the Terminal Launcher tool. For more information, see Novell SecureLogin 6.0.SP1 Administration Guide.
Has additional SSO tools, such as the Window Finder and LoginWatch, which help you SSO-enable even the most difficult applications. For more information, see Novell SecureLogin 6.0.SP1 Administration Guide.

Stores the login information requirements for applications including:

Credentials, including but not limited to:

Username

UserID

LoginID

Password

PINs

Domain

Database names

Server IP address

Responses to dialog boxes, messages and windows events, such as:

Incorrect credentials

Password expiration and reset

Error messages, including non-compliance to password rules

Account locked

Database unavailable

Before SecureLogin can SSO-enable an application for a particular user, it must “learn” a user’s application credentials so it can encrypt and store them for future logins unless it is used in conjunction with Identity Management solutions such as IBM Tivoli.

When a user starts an application for the first time after it has been SSO-enabled, 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 logons.

Automated SSO is achieved using proprietary application definitions. Application definitions are managed in directory environments through SecureLogin management utilities, including the Administrative Management Utility, iManager plug-ins, and Active Directory MMC snap-ins. Locally and in stand-alone deployments, application definitions are managed in the Personal Management Utility or distributed using the advanced offline signed and encrypted method.

SSO-enabled applications 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 SSO-enabled, it is added and maintained in the Applications Properties Table.

For detailed procedures about enabling applications and Web sites for SSO, see Novell SecureLogin 6.0.SP1 Administration Guide