SecureLogin 8.1 supports .NET Framework 3.5 SP1 and later. However, the .NET Framework should already exist for SecureLogin to use it. So, ensure that the framework is available in your system before installing SecureLogin 8.1 or upgrading to SecureLogin 8.1.
You cannot enable single sign-on for applications that are built in on non-natively supported UI framework such as Microsoft .NET framework, Gecko, and QT.
For example, applications such as Mozilla Thunderbird 2.0.0.18, Novell iFolder cannot be enabled for single sign-on using the Wizard. The Wizard fails to detect the control to enable these applications. You can however, enable single sign-on for such applications without using the Wizard.
For some applications, such as Mozilla Thunderbird, though you can use the keystrokes, SecureLogin identifies the login fields wrongly. It identifies both the username and password fields only when the password dialog box appears.
To resolve this problem, deselect the Navigate to field using keystroke option for the username and proceed to enable single sign-on.
The buttons in Windows applications that contain QT controls are displayed as Edit fields.
This incorrect identification is because all QT controls are part of an unsupported Windows class framework, QWidget. As buttons are also QWidgets, they are identified and displayed as Edit fields.
You cannot use the Application Definition Wizard password notification if the application displaying the password notification, such as invalid credentials is different from the application displaying the credentials.
For example, application definition for Novell iPrint Client fails because the Windows Wizard does not detect failed authentication.
This is a limitation in the design of the Wizard. The application prompting for credentials is different from the application displaying the authentication failure. The Wizard does not support this and it is handled by the SetPlat script. For information about the SetPlat
script, see the NetIQ SecureLogin CE 24.3 (v9.2) Application Definition Guide.
NOTE:The limitation applies to all applications where the notification dialog box is different from the application used by the Wizard.
If you have deployed SecureLogin in the Standalone mode, you cannot specify re-authentication rules. The re-authentication rule does not apply to SecureLogin in the Standalone mode. The Application Definition Wizard does not recognize the mode of deployment.
The Application Definition Wizard cannot define login notifications such as incorrect password or incorrect login that are displayed through browser pop-ups in Mozilla* Firefox*. The Application Definition Wizard considers the popup windows as URL and tries to add them to the already defined definition for that URL.
SecureLogin might not pass the correct domain name while performing a single sign-on operation for the Microsoft Windows Vista Remote Desktop client in either the Novell Client or LDAP mode.