Enterprise Single Sign-on

Quest Enterprise Single Sign-on s'attaque à des domaines clés tels que l'efficacité, la sécurité et la conformité dans des environnements complexes avec de multiples applications et systèmes nécessitant une connexion. Il vous permet de :

• Baser l'authentification unique sur Active Directory : base le processus d'authentification unique et la gestion d'accès de toute l'entreprise sur les identités, les groupes et les règles existants dans le système Active Directory déployé sans nécessiter aucune autre méthode d'authentification ou la mise en place d'un « métarépertoire ». 
• Garantir la sécurité et le respect des règles d'accès dans toute l'entreprise : utilise les stratégies d'accès et les règles Active Directory pour appliquer des contrôles similaires au processus d'authentification unique axé sur le client, et ce pour l'ensemble des applications et systèmes auxquels l'utilisateur peut avoir besoin d'accéder.
• Mettre en place un unique point d'authentification puissante pour l'ensemble des ressources : fournit un point unique de connexion/d'authentification des utilisateurs pour tous les systèmes et applications. Cela inclut les connexions standard avec identifiant/mot de passe, ainsi que toute la gamme d'options d'authentification puissante comme par exemple les cartes intelligentes, la biométrie ou l'authentification à double facteur avec jeton.
• Améliorer l'efficacité du service informatique et de l'utilisateur final : soulage l'équipe informatique du poids que constituent la gestion d'accès des utilisateurs et la réinitialisation des mots de passe dans de nombreux types d'applications.
• Être en conformité : il répond aux exigences de conformité les plus courantes en matière de gestion d'accès, d'authentification renforcée et de délégation sécurisée des droits d'accès en mettant en place une infrastructure cohérente et solide basée sur Active Directory pour respecter les règles d'accès.

Client-Side Modules

Advanced Login, Enterprise Console, SSOWatch, Token Manager

Audit Database
ESSO Console can store a "master" audit database on a relational database. ESSO Console has been validated with the following configurations:

The size of the hard drive hosting the audit database depends on how long you want to keep the log online before archiving it. (The audit database does not need to reside on the ESSO Console server itself.) For a rough estimate use the following:

• One log entry = 1000 bytes (including database index and other overhead)
• Typical log activity = 20 log entries per user per day.

LDAP Directories

Enterprise Single Sign-On can access user information located in LDAP directories and use these directories to store SSO and security data. The following directories are supported:

Enterprise Single Sign-On can use Microsoft Active Directory Application Mode (ADAM) to store SSO and security data. ADAM version 1.1 (Service Pack 1) or higher is required. ADLDS included with Windows Server 2008 is also supported.

Using Enterprise Single Sign-On with Samba

Enterprise Single Sign-On can be installed in an environment where Samba is used as an authentication server and domain controller. The prerequisites are:

• Samba must be version 3.0.x
• Samba must use OpenLDAP (see version above)

Supported Authentication Devices

Smart Cards and USB Tokens

The middleware and authentication devices listed below are used by these specific Enterprise Single Sign-On modules:

• Advanced Login can use the devices for user authentication.
• Token Manager and ESSO Console can manage these devices.
• Token Manager and ESSO Console can use these devices for administrator authentication.

When using smart cards, you must use PC/SC smart card readers that are compatible with both the cards and the middleware detailed above.
The only Certification Authority that is supported at the moment is the Microsoft Windows 2000/2003/2008 Certification Authority in an Active Directory configuration. Other Certification Authorities can be used via the PKCS import feature of ESSO Console and Token Manager.

Biometric Devices

Biometrics support requires that you purchase from Precise Biometrics a license of Precise BioMatch Pro Toolkit 2.3.0 for each workstation where biometric authentication will be performed;
The list of biometric devices supported by Precise BioMatch Pro Toolkit 2.3.0 is currently the following;

• Precise 100 A/AX/SC/MC/XS/BioKeyboard/PC-Card
• Precise 200 MC
• Precise 250 MC
• IRIS BCR100T
• IRIS Mobile SmartTerm St4E
• AuthenTec AES4000 API-based readers
• AuthenTec AES2501 API-based readers
• Cherry FingerTip Keyboards
• UPEK ST1
• UPEK ST2
• silex FUS-200N
• silex MUSB-200-COMBO
• silex COMBO-mini

Warning: some of these devices require a specific license of the Precise Biometrics software. Determine with the vendor which license is appropriate.
For an up-to-date list, contact Precise Biometrics at http://www.precisebiometrics.com.

RFID/HID Devices

XyLoc support requires that you obtain from Ensure Technologies the Software Development Kit in order to deploy on each workstation the ETSecure.dll. E-SSO has been tested with the following MIFARE components:

• SAGEMYpsid S1-IAS
• Sagem YPsid MatchOnCard
• GemSafeYpresso 64K (Classic TPC)
• Oberthur
• Cyberflex 64K
• Crypto.NET v2+

These tests have been done with the following reader: CardMan 5321, these RFID devices are natively supported (no middleware needed)
E-SSO is pre-configured with the following ATR (Answer To Reset):

Warning: Xyloc devices are not supported with Microsoft RDP.

SSOWatch Plug-in Requirements

General

Plug-ins are extensions of SSOEngine and SSOStudio. They provide SSO authentication methods for specific types of applications.
These plug-ins are delivered with SSOWatch. Plug-ins are available for:

• Microsoft Internet Explorer (for Internet Explorer 5.5, 6.0,7.0 and 8.0)

• Firefox 1.5, 2.0, and 3.0.4 and higher (warning, due to an issue Firefox 3.0.0 to 3.0.3 are not supported)
• Sun Java SE Runtime Environment (JRE) 1.4, 1.5 and 1.6
• Lotus Notes versions 4.x, 5.x and 6.5
• Microsoft Telnet
• HLLAPI (see Configuring the HLLAPI Plug-in section for supported emulators)
• SAP R/3 client version 6.20
• SAP R/3 client version 6.20
• Script environment for Windows and HTML applications that are not covered by the standard WiseGuard process

SSOWatch SAP R/3 Plug-in Requirements

Plug-ins are extensions of SSOEngine and SSOStudio. They provide SSO authentication methods for specific types of applications.
These plug-ins are delivered with SSOWatch. Plug-ins are available for:

Important: The SAP web-based Start Center is compatible with Enterprise Single Sign-On, but you need to upgrade to SAPGUI Version 6.40 with Patchlevel 23.

The SAPLogin and SAPExpired window types defined in version 3.71 of SSOWatch remain available to ensure the continuity of deployed configurations. We recommend not using them for new deployments. Existing windows should be ported to SAPGUI Scripting window types.

Supported HTTP Server

The following Enterprise Single Sign-On features require HTTP server:

• Web Service administration API
• Password reset feature

Important: We strongly recommend using the HTTP server delivered on the Enterprise Single Sign-On CD. Only this HTTP server (based on Apache 2.0) is supported by Quest Software. No support for the above-mentioned features will be provided when used with any other server. As well, Quest Software will not support the bundled server for functions other than those that are strictly necessary for the abovementioned Enterprise Single Sign-On features.
The password reset feature requires you to use a certificate generated by a Certification Authority (CA) in order to activate HTTPS. For evaluation purposes, a sample CA is delivered on the product CD, without any further support for that CA. Please use a supported CA for actual deployments.

• Product Demo

  vWatch the Demo »

• Quest on the Board: Single Sign-On

  Todd Peterson presents this white board session which examines the four types single sign-on offerings from Quest.

  Watch the White Board Session »