Novell SecureLogin application definitions provide the following advantages:
Enables you to define single sign-on methods for almost any Windows, mainframe, Internet, Web, Terminal Server, or UNIX* application.
You do not need to install back-end modules on your application servers.
Provides the flexibility for you and your application owners to choose what to do once an application generated message is detected, giving you full control over your single sign-on environment.
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.
Allows you to implement auditing to meet your requirements.
SecureLogin data such as user credentials is stored and protected in the directory. The credentials are also stored in the smart card or in the cache; depending on the configuration:
If store credentials on a card are set, then your credentials are on the card and in the directory. The cache file contains only the application definition.
If the cache file is disabled, only the credentials are stored in the directory.
On startup, Novell SecureLogin performs the following tasks:
Locates these objects in the directory.
Caches their encrypted contents in memory (and optionally on disk) for later use by the workstation's SecureLogin agent.