Enterprise Single Sign-on

Quest Enterprise Single Sign-on利用多个基于登录的应用程序和系统，帮助您解决复杂环境中主要的效率、安全与合规问题。 它可让您：

• 在Active Directory之上建立单点登录：将整个企业的单点登录和访问控制建立于部署在现有Active Directory中的身份、组和策略的基础之上，无需使用额外的验证方法或执行元目录。 
• 强化整个企业的安全和访问政策：利用现有的访问策略和Active Directory规则，针对用户可能需要访问的所有应用程序和系统，实施基于客户端单点登录的类似控制。
• 为所有资源提供单点强认证：为任何系统和应用程序提供单点用户登录验证。 包括标准的用户名或密码登录和所有强认证选项，例如智能卡、生物辨识系统、基于令牌的双因子身份验证。
• 提高IT和终端用户效率：帮助IT人员摆脱管理各种应用程序的用户访问和密码重设的繁重工作。
• 实现合规要求：通过部署基于Active Directory的统一而强大的基础架构来实施访问策略，满足对访问控制、强认证和访问权限安全授权的一般性合规要求。

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 »