엔터프라이즈 싱글 사인-온

퀘스트 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 »