Chat now with support
Chat with Support

Enterprise Single Sign-On 8.0.6 - Advanced Login for Windows User Guide

1 Overview 2 Logging on to Windows 3 Locking/Unlocking Your Windows Session 4 Switching Users Without Logging Off Windows (Fast User Switching) 5 Displaying Session Information (Windows XP/2003 only) 6 Shutting Down Your Workstation (Windows XP/2003 only) 7 Managing Your Password or PIN 8 Managing the Unblocking of Your Smart Card 9 Managing Your Windows Session Accounts 10 Managing Primary Accounts on Your Smart Card 11 Renewing your Smart Card Certificate(s) 12 Managing a Cluster from Your Workstation 13 Managing Session Delegation 14 Deleting Your Roaming Session 15 Logging on as an Administrator on a User Session Appendix A: Advanced Login Registry Keys Appendix B: Integrating Quest ESSO with Prim'X Cryhod

B.1 Configuring the Integration

Full path name of the Windows DLL. The file is called DiskEncryptionCryhod.dll and is installed in the same directory as the
Quest ESSO Client.
SHA-256 hash values for DiskEncryptionCryhod.dll. They are displayed in the DiskEncryptionCryhod.txt file, located in the Quest ESSO Client installation directory. Depending on the architecture of your Windows workstations, you may need the hash values for 32 and/or 64-bit systems.
Name the value as recommended: E-SSO CREDAPI Extension Vx.y (zz-bit) and use these elements to set the Cryhod policy P880 - Software Extensions with Microsoft Windows GPO.
Common\Extensions key is generated in the Microsoft Windows registry of each workstation.
This key contains a value of type
String corresponding to the version of DiskEncryptionCryhod.dll used on the local workstation. If the key contains multiple values corresponding to different versions of DiskEncryptionCryhod.dll, only the value that matches a file on the local workstation is used.

B.2 Customizing the Integration

It is possible for an Quest ESSO Smart Card tile to be selected before Cryhod passes the PIN to Quest ESSO. In this case, Quest ESSO waits for a few seconds for the PIN to be passed. If the PIN is not passed in time, the user has to provide it, thus typing the PIN twice.
To avoid this, the length of time that Quest ESSO waits for the PIN can be configured using a Windows registry value.
Create the DWORD value WaitForPINDuration under one of the following keys:

B.3 Cryhod Log Files

An event is recorded in the Cryhod event log each time DiskEncryptionCryhod.dll is used. The event includes a result code indicating the reason for any failure to pass the PIN.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating