4.0 Enabling Applications and Websites for Single Sign-On

SecureLogin has predefined applications for single sign-on (SSO) access to a wide range of commercially available applications.

SecureLogin detects applications for which a predefined application exists. For example, if SecureLogin detects Novell GroupWise Messenger dialog box, then it prompts the user to allow SecureLogin to enable SSO for the application.

Predefined applications for some commonly used applications are incorporated with SecureLogin, and with each new version, more applications are developed and made available to the customers.

SecureLogin provides application definition wizard to facilitate SSO to almost any new or proprietary application, if a predefined application is unavailable. For information, see the NetIQ SecureLogin 9.0 Application Definition Wizard Administration Guide.

SecureLogin also supports enabling SSO for terminal emulator applications.

  • Users can enable SSO for terminal emulators by using the terminal launcher tool.

  • SecureLogin has additional tools such as, Window Finder and LoginWatch, which help the user to enable SSO for even the most difficult applications. For information, see the NetIQ SecureLogin 9.0 Application Definition Guide.

SecureLogin stores the login information requirements for applications including the following:

Credentials, but not limited to:

  • Username

  • UserID

  • LoginID

  • Password

  • PINs

  • Domain

  • Database names

  • Server IP address

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

  • Login

  • Incorrect credentials

  • Password expiration, including non-compliance to password rules

  • Account locked

  • Database unavailable

Before SecureLogin can enable an application for SSO 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 Identity Manager.

When a user starts an application for the first time after it is enabled for SSO, 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 SSO is achieved by using the proprietary application definitions. The application definitions are managed in directory environments through SecureLogin administrative management utilities. In local and standalone deployments, the application definitions are managed in SecureLogin Client Utility or distributed by using the advanced offline signed and encrypted method.

The SSO applications are created, modified, and deleted in the Applications pane. Users can also create application definitions with SecureLogin Wizard. 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 SSO, it is added and maintained in the Applications properties table.