etoken Single Sign-On ReadMe Version 5.1 Rev A Release Date: May 2010 ======================================================

Transcription

1 etoken Single Sign-On 5.1 Read Me 1 etoken Single Sign-On ReadMe Version 5.1 Rev A Release Date: May 2010 ====================================================== This document contains last minute information about the etoken SSO 5.1 release. We recommend reading the following documents before implementing the solution: etoken SSO 5.1 Administrator s Guide etoken SSO 5.1 User s Guide Contents 1. Support Licensing New Features Installing etoken SSO and etoken WSO on the Same Computer Installation Packages Default Password Resolved Issues Known Issues Support We work closely with our reseller partners to offer the best worldwide technical support services. Your reseller is the first line of support when you have questions about products and services. However, if you require additional assistance you can contact us directly: Telephone You can call our help-desk 24 hours a day, seven days a week: USA: International: You can send a question to the technical support team at the following address: support@safenet-inc.com Website You can submit a question through the SafeNet Support portal:

2 etoken Single Sign-On 5.1 Read Me 2 2. Licensing The use of this product is subject to the terms and conditions as stated in the End User Agreement. 3. New Features The following new features were introduced in this release: Extended platform support Windows 7 (32-bit) The etoken TMS 5.1 SSO Connector supports TMS installation (both TMS Management Tools and TMS Server) on 64 bit platforms Updated browsers support Internet Explorer 8.0 Firefox 3.5 Optional automatic profile backup 4. Installing etoken SSO and etoken WSO on the Same Computer Installing etoken SSO and etoken WSO on the same computer is not recommended as this may lead to unpredictable behavior of the applications. 5. Installation Packages The following installation packages are supplied: etoken SSO Package (etokenssopackage51_x86.exe) Installs or upgrades any combination of the following applications: etoken PKI Client-Lite or etoken PKI Client etoken SSO etoken Network Logon etoken SSO Template Editor etoken SSO (etsso51_x86.msi) etoken SSO Template Editor (etssote51_x86.msi) TMS 5.1 Connector for etoken SSO (TMS51SSO51con_x86.msi or TMS51SSO51con_x64.msi) 6. Default Password All etoken devices are shipped from our factory with a default etoken Password etoken Virtual files are assigned the same default etoken Password. End users must enter this default password the first time they log on to etoken, and then change it to a secure personal password.

3 etoken Single Sign-On 5.1 Read Me 3 7. Resolved Issues This section lists resolved issues in this release. Description/Resolution When using the etoken SSO Template Editor on Internet Explorer with a content of Flash, the etoken SSO Template Editor crashes. In the TMS Connector s Guide, an incorrect registry path (HKLM\SOFTWARE\Aladdin\eToken\TMS\ Server\ SsoConnector) is listed for the etoken SSO connector. If etoken SSO is started when the user hard disk is full, etoken SSO is denied write access to the template folder. The message displayed should be changed. When you enable "AllowChangeURL" with etoken SSO 3.14, and then copy a profile, the "Form" in the new profile does not change until you double-click it. URLs are not checked by WSO (part of etoken SSO). During profile selection, the Select Profile list includes profiles that are not relevant. When backing up profiles to a new file that does not exist, a warning message is displayed. Unable to create templates for Command Prompt windows (blind template). In the etoken SSO 5.1 Administrator s Guide, the path was corrected to HKEY_LOCAL_MACHINE\SOFTWAR E\Aladdin\eToken\TMS\SsoConnec tor. The new message is: There is not enough space on the disk. for all new profiles 8. Known Issues This section lists known issues in this release On Windows 7: If a non-administrator installs the complete etoken SSO package, and then opens the Internet Explorer browser and opens the profile selection menu, Internet Explorer crashes. Log off the computer, and then log on again.

4 etoken Single Sign-On 5.1 Read Me , , Run the etoken SSO or etoken SSO Package command line installation with the parameter to create an etoken Virtual. Include the parameter /qn or /qb or /s. etoken SSO is installed, but an etoken Virtual is not created. After enrolling tokens using TMS, the profiles are not always visible in etoken SSO. Installing etoken SSO and etoken WSO on the same computer causes unpredictable behavior of the applications. Cannot install the TMS Connector for etoken SSO 5.1 on a TMS 2.0 server. Sometimes, the etoken SSO Package fails when upgrading etoken PKI Client- Lite. The etoken SSO 3.14 installation included etoken Network Logon functionality. When the etoken SSO 5.1 Package without etoken Network Logon upgrades etoken SSO, all previously installed etoken Network Logon functionality is lost. During the etoken SSO Template Editor installation on Windows 7, if an etoken SSO file to be updated is in use, the user is prompted to select Exit, Ignore, or Retry. However, the Ignore button is disabled, so the installation process cannot continue. Sometimes, the Automatic Backup feature does not work in Windows 7. To run the etoken SSO command line installation in quiet mode, use the parameter /qr or /qf. Refresh the etoken SSO window, and the profiles are displayed. Do not install etoken SSO and etoken WSO on the same computer. When running TMS 2.0 with etoken SSO 5.1, use the TMS Connector for etoken SSO Ensure that no tokens are connected during the upgrade. If a token is connected, the installation fails. You must restart the computer, and then rerun the upgrade. During the upgrade to 5.1, select etoken Network Logon in the etoken SSO Package installation. Use the Task Manager to end the process that uses the file, and then click Retry to continue the installation. Ensure that the backup file is saved to an existing folder, either on the same computer or in the shared network path, where the user has sufficient permissions to read and write.

5 etoken Single Sign-On 5.1 Read Me , Saving an etoken SSO profile fails when using Firefox on a computer with McAfee AntiVirus installed. Installing TMS Connector for etoken SSO 5.1 fails if a version of etoken Template Editor earlier than 5.1 is installed. After installing etoken SSO on Windows Server 2008, the etoken SSO Toolbar does not appear in Internet Explorer. When logging onto a website with a saved profile, the Create Profile window may open, even though the profile already exists. After installing etoken SSO, the etoken PKI Client tray icon may fail to appear. When creating a profile based on a template with two forms, there is a delay after saving the first form before the second form opens. When installing etoken SSO on Windows Vista, the Files in Use window may open with a prompt to close certain applications. Some web profiles created in Firefox are not supported by Internet Explorer, and vice versa. If the token is removed from the client computer while being logged on to a remote server, an error message Invalid Token may be displayed instead of the expected Unlock Computer window. In some cases the Auto submit function does not work when the user has more than one profile for the same screen. Port 6668 (default for Firefox) is blocked by McAfee AntiVirus. Change the port to an unblocked one (for example 10668). Install the TMS Connector for etoken SSO Re-boot the computer, and then manually install the etoken SSO toolbar. From the browser menu, select Tools > Toolbars > Explorer Bar > etoken SSO. Click Cancel. Restart the computer or restart the etoken PKI Client tray icon process (PKIMonitor.exe). Wait for the second form to open. The process will then proceed correctly. Click Ignore, and continue the installation. The user is prompted to create a dedicated profile for Internet Explorer and Firefox. Click OK on the error message. The Unlock Computer window opens. The user can choose which profile to use for logging on.

6 etoken Single Sign-On 5.1 Read Me If, after saving a web page to the token, the etoken Password is changed and a different web page is saved, an unclear message Log on with a new password is displayed. Certain sites do not support automatic submit. The credentials for these sites are filled automatically, but are not automatically submitted. The etoken SSO toolbar must be manually added and removed for Firefox users. Unable to turn Auto Submit on or off for all applications at the same time. Change password for web profile: Web applications using the same URL for password changing and logon are not supported. Web applications using dynamic URLs (URLs that are dynamically changed) are not supported. Sometimes, basic etoken SSO functions stop responding. (For example: automatic fill or automatic save) When creating a profile based on a template, the process may stop responding. The autosave function does not operate with some webpages. Remove and then reconnect the token. The user must manually press the submit button. In Firefox, the etoken SSO toolbar must be installed and uninstalled manually for each user. The disable Auto Submit procedure must be performed for each web profile separately. None To resume normal etoken SSO operation, select. Start >Programs>eToken>eToken SSO>Resume etoken SSO. Select Start >Programs>eToken>eToken SSO>Resume etoken SSO. Click the Save Web Profile icon on the etoken SSO toolbar.