Oracle® Fusion Middleware

Deploying Logon Manager with a Directory-Based Repository

11g Release 2 (11.1.2.2)

E37700-01

December 2013

Oracle Fusion Middleware Deploying Logon Manager with a Directory-Based Repository, 11g Release 2 (11.1.2.2)

E37700-01

Copyright © 1998, 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Deploying Logon Manager with Microsoft Active Directory

- 1.1 Logon Manager and Active Directory Environments

- 1.1.1 How Logon Manager Extends Your Active Directory Schema

- 1.1.2 How Logon Manager Synchronizes with Active Directory

- 1.1.3 How Logon Manager Handles and Stores Application Credentials

- 1.1.4 Further Reading

- 1.2 Designing the Logon Manager Active Directory Sub-Tree

- 1.2.1 Guidelines for Structuring the Sub-Tree

- 1.2.2 Version Control and Pre-Flight Testing of Templates and Policies

- 1.2.3 Precautions for Configuring Object Access Control Lists Using the Console

- 1.2.4 Precautions for Upgrading the Agent and Console

- 1.3 Global Agent Settings vs. Administrative Overrides

- 1.4 Recommended Global Agent Settings

- 1.4.1 Data Storage Settings

- 1.4.1.1 Use Configuration Objects

- 1.4.1.2 Specify the Path to the Logon Manager Configuration Objects

- 1.4.1.3 Store User Credentials Under Respective User Objects

- 1.4.2 Repository Connection Settings

- 1.4.2.1 Let Logon Manager Find the Nearest Domain Controller

- 1.4.2.2 SSL Support

- 1.4.2.3 Select the Credentials to Use when Authenticating to the Directory

- 1.4.2.4 Decide Whether to Prompt the User when Disconnected from the Directory

- 1.4.2.5 Let Logon Manager Search for User Accounts

- 1.4.2.6 Add the Active Directory Synchronizer to the Synchronizer Order List

- 1.4.2.7 Make the Logon Manager Agent Wait for Synchronization on Startup

- 1.4.2.8 Use Optimized Synchronization

- 1.4.3 Restrict Disconnected Operation

- 1.5 Recommended Administrative Overrides

- 1.6 Overview of the Deployment Process

- 1.7 Preparing Active Directory for Logon Manager

- 1.7.1 Extending the Schema

- 1.7.2 Enabling the Storage of User Credentials under User Objects

- 1.7.3 Creating the Configuration Object Container and Sub-Tree Structure

- 1.8 Configuring the Active Directory Synchronizer

- 1.9 Testing the Logon Manager Configuration

2 Deploying Logon Manager
with Microsoft AD LDS (ADAM)

- 2.1 Logon Manager and AD LDS (ADAM) Environments

- 2.1.1 Benefits of AD LDS (ADAM)-Based Deployments

- 2.1.2 Active Directory vs. AD LDS (ADAM)

- 2.1.3 How Logon Manager Extends the AD LDS (ADAM) Schema

- 2.1.4 How Logon Manager Synchronizes with AD LDS (ADAM)

- 2.1.5 How Logon Manager Handles and Stores Application Credentials

- 2.1.6 Benefits of Load-Balancing an Logon Manager Deployment

- 2.1.7 Further Reading

- 2.2 Designing the AD LDS (ADAM) Directory Sub-Tree

- 2.2.1 Guidelines for Structuring the AD LDS (ADAM) Sub-Tree for Logon Manager

- 2.2.2 Version Control and Pre-Flight Testing of Templates and Policies

- 2.2.3 Precautions for Configuring Object Access Control Lists Using the Console

- 2.2.4 Precautions for Upgrading the Agent and Console

- 2.3 Global Agent Settings vs. Administrative Overrides

- 2.4 Recommended Global Agent Settings

- 2.4.1 Use Configuration Objects

- 2.4.2 Configure a Server List with Desired Failover Order

- 2.4.3 Specify the Path to the Logon Manager Configuration Objects

- 2.4.4 SSL Support

- 2.4.5 Select the Credentials to Use when Authenticating to the Repository

- 2.4.6 Configure Logon Manager to Use a Specific People OU

- 2.4.7 Choose Whether to Prompt the User when Disconnected from the Repository

- 2.4.8 Add the AD LDS (ADAM) Synchronizer to the Synchronizer Order List

- 2.4.9 Make the Logon Manager Agent Wait for Synchronization on Startup

- 2.4.10 Use Optimized Synchronization

- 2.4.11 Restrict Disconnected Operation

- 2.5 Recommended Administrative Overrides

- 2.6 Overview of the Deployment Process

- 2.7 Creating an AD LDS (ADAM) Instance

- 2.8 Preparing the AD LDS (ADAM) Instance for Logon Manager

- 2.8.1 Extending the Schema

- 2.8.2 Creating the People OU

- 2.8.3 Creating the Configuration Object Container and Sub-Tree Structure

- 2.8.4 Granting Required Permissions to Logon Manager Users

- 2.9 Configuring the AD LDS (ADAM) Synchronizer

3 Deploying Logon Manager with an LDAP Directory

- 3.1 Logon Manager and LDAP Environments

- 3.1.1 How Logon Manager Extends Your Directory Schema

- 3.1.2 How Logon Manager Synchronizes with Your Directory

- 3.1.3 Benefits of Load-Balancing a Logon Manager Deployment

- 3.1.4 How Logon Manager Handles and Stores Application Credentials

- 3.1.5 Further Reading

- 3.2 Designing the Logon Manager Directory Sub-Tree

- 3.2.1 Guidelines for Structuring the Logon Manager Sub-Tree

- 3.2.2 Special Directory Objects Required by Logon Manager

- 3.2.3 Version Control and Pre-Flight Testing of Templates and Policies

- 3.2.4 Precautions for Configuring Object Access Control Lists Using the Console

- 3.2.5 Precautions for Upgrading the Agent and Console

- 3.3 Global Agent Settings vs. Administrative Overrides

- 3.4 Recommended Global Agent Settings

- 3.4.1 Select the Correct Repository Type

- 3.4.2 Configure a Server List with Desired Failover Order

- 3.4.3 Specify the Path to the Logon Manager Configuration Objects

- 3.4.4 Use Configuration Objects

- 3.4.5 SSL Support

- 3.4.6 Specify the Path(s) to User Accounts

- 3.4.7 Enable Directory Search for Users

- 3.4.8 Set the Naming Attribute String

- 3.4.9 Decide Whether to Prompt the User when Disconnected from the Directory

- 3.4.10 Share LDAP Synchronizer Credentials with Authenticators

- 3.4.11 Add the LDAP Synchronizer to the Synchronizer Order List

- 3.4.12 Set the Authentication Prompt Window Title

- 3.4.13 Make the Logon Manager Agent Wait for Synchronization on Startup

- 3.4.14 Use Optimized Synchronization

- 3.4.15 Restrict Disconnected Operation

- 3.5 Recommended Administrative Overrides

- 3.6 Overview of the Deployment Process

- 3.7 Preparing the Directory for Logon Manager

- 3.7.1 Extending the Schema

- 3.7.2 Creating the Sub-Tree Root and the Configuration Object Container

- 3.7.3 Creating the People OU

- 3.7.4 Creating the vGOLocator Pointer Object

- 3.8 Selecting and Configuring an Authenticator

- 3.9 Configuring the LDAP Synchronizer

4 Appendix A: Minimum Administrative Rights for Logon Manager Repository Objects

- 4.1 Minimum Administrative Rights Required by Logon Manager Containers

- 4.2 Minimum Administrative Rights Required for Credential Auditing

- 4.3 Minimum Administrative Rights Required for Credential Deletion

5 Appendix B: Logon Manager Repository Object Classes and Attributes

- 5.1 vGOUserData

- 5.2 vGOSecret

- 5.3 vGOConfig

- 5.4 vGOLocatorClass

6 Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory

- 6.1 Active Directory Schema Extension Failures

- 6.2 All Users Unable to Store Credentials Under User Objects

- 6.3 Select Users Unable to Store Credentials Under User Objects

7 Troubleshooting Logon Manager
on Microsoft AD LDS (ADAM)

- 7.1 The Target AD LDS (ADAM) Instance is Not Running

- 7.2 AD LDS (ADAM) Instance is Running on Non-Default Ports

- 7.3 Account Used to Connect to AD LDS (ADAM) Does Not Have the Required Privileges

8 Appendix E: Creating the Required User Groups on AD LDS (ADAM)

9 Appendix F: Configuring Oracle Internet Directory

10 Appendix G: Configuring Oracle Virtual Directory

Preface

This guide describes best practices and recommended procedures for deploying Oracle Enterprise Single Sign-On Logon Manager with Microsoft Active Directory, Microsoft AD LDS (ADAM), and an LDAP directory such as Oracle Internet Directory.

Audience

This guide is intended for experienced administrators responsible for the planning, implementation and deployment of applications. Administrators are expected to have solid knowledge of directory environments, permission structures, domain administration, and databases.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle Enterprise Single Sign-On Suite Release 11.1.2.2 documentation set:

- Oracle Enterprise Single Sign-On Suite Release Notes

- Oracle Enterprise Single Sign-On Suite Installation Guide

- Oracle Enterprise Single Sign-On Suite Administrator's Guide

- Oracle Enterprise Single Sign-On Suite Secure Deployment Guide

- Oracle Enterprise Single Sign-On Suite User's Guide

- Configuring and Diagnosing Logon Manager Application Templates

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Deploying Logon Manager with Microsoft Active Directory

This chapter describes the prerequisites and procedures required to successfully deploy Logon Manager with a Microsoft Active Directory-based data repository.

1.1 Logon Manager and Active Directory Environments

Oracle Enterprise Single Sign-On Logon Manager (Logon Manager) is a secure and easily deployable single sign-on solution that acts as a middle layer between the user and the target applications. Users need to authenticate only once; Logon Manager automatically detects and handles all subsequent requests for user credentials. For more information on Logon Manager, see the Oracle Enterprise Single Sign-On Suite Technical Overview white paper available from Oracle Support.

You have the choice to deploy Logon Manager in a directory environment, such as Active Directory, which enables the delivery of single sign-on capability to any machine on the network through central storage of application credentials, templates, and policies. Users synchronize with the directory to download these items and update their credential stores with new or changed usernames and passwords.

Adding Logon Manager to your existing directory environment provides the following benefits:

- Logon Manager leverages the existing user accounts, groups, and native directory permissions (ACLs) without the need to manage these items separately or synchronize them with another directory or database.

- Logon Manager data is automatically protected by your existing backup, failover, and disaster recovery plans.

- No dedicated servers or server-side processes are required; Logon Manager's scalability and performance depend solely on the capacity and robustness of your existing directory infrastructure.

- Administrators are not burdened with additional administrative tasks or the need to learn new tools or concepts. Delegated administration of Logon Manager is achieved through the native capabilities of the directory.

- A directory also enables the organization of Logon Manager templates and policies into a highly visual hierarchy. While you can use a flat model if your environment calls for it, a properly set-up hierarchy can help maintain top directory, Agent, and network performance, as well as simplify Logon Manager administration by permitting more efficient access control.

1.1.1 How Logon Manager Extends Your Active Directory Schema

Before Logon Manager can store data in Active Directory, you must extend your Active Directory schema using the Administrative Console. The schema extension consists of adding four object classes and setting the appropriate permissions so that objects of those types can be created, read, modified, and deleted. Existing classes and attributes are not modified in any way. If you decide to allow Logon Manager to store application credentials under user objects (a recommended best practice), Logon Manager will also apply the permissions required by this feature.

Note:

Note: Schema extension is a post-installation procedure. For instructions, see Extending the Schema. Oracle highly recommends that you perform a schema health check using tools such as Microsoft MOM before performing the schema extension.

For detailed information on the schema extensions made by Logon Manager, see the following appendices:

- Appendix A: Minimum Administrative Rights for Logon Manager Repository Objects

- Appendix B: Logon Manager Repository Object Classes and Attributes

1.1.2 How Logon Manager Synchronizes with Active Directory

The Logon Manager Agent uses the Active Directory synchronizer plug-in to communicate with Active Directory. When properly configured, synchronization occurs whenever one of the following events takes place:

- The Logon Manager Agent starts.

- Application credentials are added, modified, or deleted by the end-user.

- The machine running the Agent acquires an IP address or its existing IP address changes. (if Logon Manager is configured to respond to these events).

- The auto-synchronize interval elapses (if configured).

- The user initiates synchronization via the Logon Manager Logon Manager's "Refresh" function.

During synchronization, the Logon Manager Agent traverses the Logon Manager tree and loads the contents of the sub-containers to which the current user has been granted access; it also synchronizes any credentials that have been added, modified, or deleted since the last synchronization.

1.1.3 How Logon Manager Handles and Stores Application Credentials

Logon Manager encrypts application credentials using a unique key generated when the user completes the First-Time Use (FTU) wizard. The credentials remain encrypted at all times, including in the Agent's local cache, the directory, and while in transit over the network. Logon Manager only decrypts credentials (to memory, never to disk) when a configured application requests logon, and wipes the target memory location as soon as the logon request completes. The amount of data Logon Manager stores per enabled application and per user is trivial (measurable in bytes and small kilobytes).

Note:

Logon Manager supports SSL encryption for directory connections. While normally not required, SSL support is necessary in certain scenarios. See SSL Support for details.

1.1.4 Further Reading

An in-depth discussion of the Logon Manager software architecture is beyond the scope of this guide. To obtain Oracle white papers containing additional information, contact your Oracle representative.

1.2 Designing the Logon Manager Active Directory Sub-Tree

Logon Manager gives you the freedom to set up the directory structure to best fit the needs of your organization. Specifically, you have the choice to store your data in a flat model, or create a hierarchy. While a flat model works fine for small deployments, growing and large deployments should utilize a hierarchy from the very beginning. The exact structure of your sub-tree will depend on the following factors:

- Number of users

- Number of applications you want Logon Manager to support

- Robustness of the existing infrastructure

- Structure of your organization

Always follow Microsoft's best practices for Active Directory design and implementation described in the following article: http://technet.microsoft.com/en-us/library/bb727085.aspx

1.2.1 Guidelines for Structuring the Sub-Tree

Oracle recommends that you set up your sub-tree as a hierarchy by following the guidelines below:

- Use OUs to group templates and policies by category, such as department or division, according to the structure of your organization.

- Control access at the OU level.

- Disable inheritance and grant no user rights at the root of the Logon Manager sub-tree, unless your environment dictates otherwise.

When set up this way, a hierarchy provides the following benefits:

· Highly visual and self-documenting tree structure. When you view your sub-tree in a directory browser, the sub-tree structure is self-descriptive and easy to follow.

- No unwanted inheritance of rights. Users will not natively inherit rights to sub-OUs you don't want them to access. This eliminates the need to explicitly deny unwanted access rights that are being passed down the tree.

- Robust network, Agent, and directory performance. Typically, users who download large numbers of templates and policies generate more network traffic and a higher load on the directory than users who only download items relevant to their jobs. Grouping conserves your environment's resources and improves Agent response time.

- Distributed administrative tasks. Your templates are organized into easily controllable sets, and access rights determine who can manage which templates. You also have the ability to implement rights-based version control of your templates.

- Low administrative overhead. Controlling access at the template level requires setting permissions for each individual template via the Logon Manager Administrative Console; controlling access at the OU level is achieved via delegated administration using Microsoft and third-party management tools.

The following figure depicts a sample Logon Manager sub-tree whose design reflects the above best practices.

In our sample scenario, users from the Portland division do not need access to applications used by the Sacramento division, and vice versa; therefore, each division's templates and policies live in dedicated sub-OUs under the root and one division cannot access another division's sub-OU. In the end, your environment will dictate the specifics of your implementation.

Note:

Oracle highly recommends that you store templates and policies in individual OUs. To do this, you must Use Configuration Objects.

If you are starting out with a flat model, but expect the number of users and provisioned applications to grow, create a sub-container under the root and use it to store your templates and policies as a flat file until you are ready to transition to a hierarchy. Monitor the performance of your environment as you add more users and provision more applications, and transition to a hierarchy sooner rather than later to minimize the required effort.

1.2.2 Version Control and Pre-Flight Testing of Templates and Policies

Oracle recommends that you create dedicated sub-OUs for each stage of your workflow: development, staging, and production, as shown in Figure 1. This way you will be able to:

- Track changes made to templates and policies as they pass through the workflow and enter production by keeping shadow copies each time templates and policies move from one workflow stage to the next.

- Roll back to a previous version of a template or policy if need arises.

- Control who can work on which templates and policies at each workflow stage. In particular, you should strictly enforce rules governing who can put a template or a policy into production.

Always test every application template and administrative override in a contained environment before you deploy it to end-users. Testing helps you stage your changes and resolve any potential issues that would be much more costly to resolve were they to occur in production. Testing is particularly critical in large deployments: if you push out a misconfigured template or an incorrect administrative override network-wide, access to mission-critical applications may be lost enterprise-wide.

When setting up a contained test environment, create a dedicated test container to which only members of your development group will have access. Then, point the test Logon Manager Agent(s) at this container and place your templates and administrative overrides in it. Once you confirm that the templates and policies are functioning as intended, move them to the target production container.

If you decide not to keep shadow copies of your templates after you test them, move them from the test container to target production containers as follows:

1. Pull down the template from the directory.

2. Create a local backup of the template.

3. Push the duplicate into the new location within the directory.

4. Delete the template from its original location.

1.2.3 Precautions for Configuring Object Access Control Lists Using the Console

When you modify an object's Access Control List (ACL) using the Console, the connection string (repository host name or IP) used to connect to the repository is treated by the Console as a unique repository identifier and recorded in the object. The Console is thus unable to distinguish between two unique repositories and two methods to connect to the same repository.

Because of this, if you use different connection strings for the same repository, e.g. an IP address and host name, the changes made to an object from one session to the next will be lost. To work around this issue in an Active Directory environment, use the repository's domain instead of a particular IP address or host name. This will ensure consistency of the connection string by allowing the Console to automatically connect to the nearest DC and changes made to object ACLs will then be retained from one session to the next.

1.2.4 Precautions for Upgrading the Agent and Console

To maintain template and settings compatibility throughout your environment, you should always use a version of the Console matching the oldest version of the Agent still deployed in production. Due to template schema changes between releases, older Agents may exhibit unexpected behavior when supplied with a template created or modified by a newer version of the Console. For this reason, if you are upgrading to a newer release of Logon Manager, Oracle highly recommends that you do not upgrade your Console until all deployed Agent installations have been upgraded.

Note:

Even if you do not make any changes to a template, it is still rewritten using the currently installed Console's data schema when you push the template back to the repository.

1.3 Global Agent Settings vs. Administrative Overrides

The behavior of the Logon Manager Agent, including its interaction with the directory, is governed by settings configured and deployed to the end-user machine by the Logon Manager administrator using the Logon Manager Administrative Console. The settings fall into one of the following categories:

- Global Agent settings are the "local policy" for the Agent; they are stored in the Windows registry on the end-user machine and are included in the Logon Manager MSI package to provide the Agent with an initial configuration during deployment. Global Agent settings are stored in HKEY_LOCAL_MACHINE\Software\Passlogix (32-bit systems) or HKEY_LOCAL_MACHINE\Wow6432Node\Software\Passlogix (64-bit systems).

Caution:

Users able to modify the HKLM hive can alter their global Agent settings and thus change the behavior of the Agent from the one originally intended. To ensure that a setting will not be changed by the end-user, deploy it through an administrative override.

- Administrative overrides take precedence over the global Agent settings stored in the Windows registry and constitute the "domain" policy for the Agent. Overrides are downloaded from the central repository by the Agent during synchronization and stored in the Agent's encrypted and tamper-proof local cache, which makes them immune to end-user alterations. When role/group security is enabled, administrative overrides can be applied on a per-user or per-group basis; they can also be applied enterprise-wide to enforce configuration consistency for all users.

Note:

Be conservative when planning your administrative overrides. Fewer overrides mean less data to store and transfer, and thus more efficient synchronization with the central repository. Reducing the number of overrides also simplifies troubleshooting by eliminating unknowns, as administrative overrides cannot be viewed on the end-user machine.

Global Agent settings together with administrative overrides constitute the complete configuration policy for the Agent. The rest of this guide describes the recommended optimal configuration and complements the information found in the Enterprise Single Sign-On Suite Administrator's Guide.

WARNING:

Settings such as domain names and user object paths should always be thoroughly tested before deployment and not deployed as administrative overrides unless absolutely necessary. A simple mistake, such as a mistyped domain name, can render end-user workstations unable to synchronize with the directory, in which case you will not be able to propagate a correction through the Console - changes will have to be made to user machines using other tools.

The following figure depicts a typical view of the Logon Manager Administrative Console set up for synchronization with Active Directory.

The next section describes best practices for configuring Logon Manager for synchronization with Active Directory. If you need additional information on settings described in this guide, see the online help included with the Console.

Note:

Before you begin, make sure that the Logon Manager Agent and the Active Directory synchronizer plug-in are installed on your machine; otherwise, AD settings will not be displayed in the Console. For installation instructions, see the Enterprise Single Sign-On Suite Installation Guide.

Tip:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

The best practice for settings not described in this guide is to leave them at their default values, unless your environment dictates otherwise. The default value is automatically in effect whenever the check box for the setting in the Administrative Console is not checked. The value is visible in the inactive field next to the check box.

1.4 Recommended Global Agent Settings

This section lists Oracle-recommended best-practice global Agent settings. Configure the settings as described below and include them in the customized Logon Manager MSI package. (For instructions on creating the package, see the section Packaging Logon Manager for Mass Deployment in the Enterprise Single Sign-On Suite Installation Guide.)

1.4.1 Data Storage Settings

Oracle recommends configuring Logon Manager's data storage settings as described below.

1.4.1.1 Use Configuration Objects

On Active Directory deployments, Oracle highly recommends that you use directory objects for storing user and configuration data, allowing hierarchical storage, as well as role/group-based access control for individual containers, templates, and policies as described in Designing the Logon Manager Active Directory Sub-Tree. If you disable this feature, Logon Manager will store all template and configuration data as a single flat file under the tree root.

Located in: Global Agent Settings > Live > Synchronization

To enable: Select the check box, then select Yes from the drop-down list.

1.4.1.2 Specify the Path to the Logon Manager Configuration Objects

You must specify the location of the Logon Manager root container (which stores Logon Manager configuration objects) for Logon Manager to store data in Active Directory.

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To set: Select the check box, click the (…) button, and enter the desired value. When you are finished, click OK.

1.4.1.3 Store User Credentials Under Respective User Objects

A major benefit of using Logon Manager with Active Directory is the ability to store user credentials under the respective user objects. Doing so simplifies administration as follows:

- Locating and viewing the credentials of individual users is quick and intuitive.

- Deleting a user from the directory automatically removes the user's application credential cache from under the respective user object.

Note:

This option will not work until you perform the necessary schema modification and permission assignment. For instructions, see Preparing Active Directory for Logon Manager.

Note:

When user credentials are stored under respective user objects and use of credential objects is enabled, you do not need to use the Locator object. (The Locator is a pointer object that tells Logon Manager where in the directory to look for templates, credentials, and other objects when using a flat directory model; for more information, see Appendix B: Logon Manager Repository Object Classes and Attributes.)

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To enable: Select the check box, then select Under respective directory user objects from the drop-down list.

1.4.2 Repository Connection Settings

Oracle recommends configuring Logon Manager's repository connection settings as described below.

1.4.2.1 Let Logon Manager Find the Nearest Domain Controller

Oracle recommends that you let Logon Manager locate and synchronize with the closest domain controller on the network, unless your environment calls for providing a specific value in this field. For example, if end-user machines are not on the same domain as the directory, you will need to provide the correct domain name. If you hardcode a complete URL in this field, you will lose fault tolerance (fallback) in the event the DC in question goes offline.

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To let Logon Manager find the nearest DC: deselect the check box (default setting).

To set: Select the check box, click the (…) button, enter the desired values (one per line) and click OK.

1.4.2.2 SSL Support

Logon Manager repository synchronizers ship with SSL support enabled and Oracle highly recommends that you do not disable it. Your environment should always utilize SSL for all connections to the Logon Manager and other repositories for maximum security.

Note:

You must configure your domain controllers to use SSL before deploying Logon Manager. For instructions, see the following MSDN article: http://msdn.microsoft.com/en-us/library/aa364671(VS.85).aspx

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To re-enable (if disabled): Deselect the check box.

1.4.2.3 Select the Credentials to Use when Authenticating to the Directory

Use the Credentials to use option to select the credentials that Logon Manager should use when authenticating to the directory. Oracle recommends that you set this to Use local computer credentials only so that the user will not be prompted to reauthenticate if Logon Manager is unable to authenticate to the directory.

Note:

Do not leave this at the default setting, Try local computer credentials; if it fails, use Active Directory server account. Doing so will cause an authentication failure (and the re-authentication prompt to appear, unless disabled) if the directory and the end-user machine are not part of the same domain.

Note:

If you are using Smart Cards to authenticate to Logon Manager, you can also use the card's certificate to authenticate to the repository by selecting Use card's certificate from the drop-down menu. For more information, see the Oracle Enterprise Single Sign-On Suite Administrator's Guide.

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To set: Select the check box, then select the appropriate option from the drop-down list.

1.4.2.4 Decide Whether to Prompt the User when Disconnected from the Directory

Use the Prompt when disconnected option to decide whether Logon Manager should prompt the user to re-authenticate to the directory upon authentication failure or disconnection. Oracle recommends that you leave this setting at its default value of No to avoid unnecessary user confusion and resulting helpdesk calls.

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To set: Select the check box, then select the appropriate option from the drop-down list.

This option is directly related to the Credentials to use option described earlier and has no effect if Allow disconnected operation is set to No.

1.4.2.5 Let Logon Manager Search for User Accounts

Oracle recommends that you let Logon Manager automatically search for user accounts in Active Directory, unless your environment calls for providing a specific value in this field. If you hardcode a path incorrectly or the path changes, you will need to update each end-user machine using tools other than the Console.

WARNING:

In production environments, this field must always be left blank to ensure fault tolerance.

Tip:

If you have only one domain, or a primary domain to which most of your users belong, specifying the domain name will save end-users the trouble of entering the domain name when authenticating to Logon Manager with their Windows password.

Located in: Global Agent Settings > Live > Synchronization > ADEXT

To let Logon Manager search for user accounts: deselect the check box (default setting).

To set: Select the check box, click the (…) button, enter the desired values (one per line), and click OK.

1.4.2.6 Add the Active Directory Synchronizer to the Synchronizer Order List

Ensure that the Active Directory (ADEXT) synchronizer plug-in is present and enabled in the Synchronizer order list if at least one of the following is true for your environment:

- Logon Manager is synchronizing with more than one repository.

- Logon Manager is using roaming synchronization.

- Kiosk Manager is installed in your environment.

Note:

Instructions for configuring Logon Manager for multi-repository and roaming synchronization, as well as installing and configuring Logon Manager, are beyond the scope of this guide. For more information, see the Enterprise Single Sign-On Suite Administrator's Guide.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then click the (…) button. In the list that appears, select the check box next to ADEXT and click OK. Use the up/down arrows to set synchronization order as necessary.

1.4.2.7 Make the Logon Manager Agent Wait for Synchronization on Startup

To ensure that users always have the most recent credentials, application templates, password policies, and administrative overrides, configure the Agent to wait for synchronization on startup. When this option is enabled, the Agent checks whether the directory is online. If the directory is online, the Agent does not respond to application logon requests until it successfully synchronizes with the directory. If the directory is offline, the Agent does not attempt to synchronize and starts immediately.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then select Yes from the drop-down list.

1.4.2.8 Use Optimized Synchronization

Optimized synchronization instructs the Logon Manager Agent to synchronize only credentials that have changed since the last synchronization. Do one of the following, depending on your environment:

- Enable this option to improve synchronization performance on deployments with large numbers of credentials per user.

- Disable this option to improve synchronization performance on deployments with fewer than five credentials per user and large number of templates downloaded per user.

Located in: Global Agent Settings > Live > Synchronization

Use the default value (Yes) unless your environment requires otherwise.

1.4.3 Restrict Disconnected Operation

During deployment, configure the Logon Manager Agent not to run if a connection to the directory cannot be established. This will prevent users from completing the First-Time Use (FTU) wizard when the Agent is not connected to the directory and no local cache is present. By not allowing the Agent to run when the directory is not available, you avoid a common situation in which a second set of encryption keys is created when a user completes the FTU wizard while disconnected from the directory.

Note:

See the "Configuring the Logon Manager Agent" section of the Oracle Enterprise Single Sign-On Suite Plus Administrator's Guide for more information on this required best practice.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then select No from the drop-down list.

1.5 Recommended Administrative Overrides

Directory synchronization settings, such as domain names and object paths, should not be deployed as administrative overrides. (See Global Agent Settings vs. Administrative Overrides for an explanation.) The recommended best-practice overrides are described in the Oracle Enterprise Single Sign-On Suite Secure Deployment Guide and in the "Configuring the Logon Manager Agent" section of the Oracle Enterprise Single Sign-On Suite Administrator's Guide.

1.6 Overview of the Deployment Process

This section provides a brief high-level overview of the Logon Manager deployment process on Active Directory. Make sure you have read all of the preceding sections of this document before proceeding with deployment. Deploying Logon Manager with Active Directory requires you to:

1. Obtain the following documents:

- The latest version of this document

- Oracle Enterprise Single Sign-On Suite Installation Guide

- Oracle Enterprise Single Sign-On Suite Administrator's Guide

2. Install the Logon Manager Agent and the Logon Manager Administrative Console on a machine within your domain, as described in the installation guide for your version of Logon Manager. Make sure you select the Active Directory Synchronizer plug-in when installing the Agent.

3. Complete the steps in Preparing Active Directory for Logon Manager:

1. Extend the Active Directory schema with Logon Manager classes and attributes.

2. Enable storage of user credentials under user objects.

3. Create the desired tree structure and grant the required permissions.

4. Configure Logon Manager as follows:

1. Complete the steps in Configuring the Active Directory Synchronizer.

2. Configure the options described in Recommended Global Agent Settings in this guide.

3. Test your configuration as described in Testing the Logon Manager Configuration.

4. Configure the options described in the "Configuring the Logon Manager Agent" section of the Enterprise Single Sign-On Suite Administrator's Guide.

Note:

For detailed descriptions of the settings in question, see the Console's online help. The online help is available via the Console's Help menu.

5. On a test machine, do the following:

- Create a pilot set of core templates and policies.

- Finalize the end-user experience by testing each core template, global Agent setting, and administrative override that will be deployed into production.

6. Create a custom MSI package and deploy it to end-user machines by completing the steps in the "Packaging Oracle Enterprise Single Sign-On Suite for Mass Deployment" section of the guide Enterprise Single Sign-On Suite Installation Guide.

7. Create, test, and deploy the remaining application templates. See the guide Configuring and Diagnosing Logon Manager Application Templates for in-depth information on provisioning different types of applications.

1.7 Preparing Active Directory for Logon Manager

This section describes the basic procedures for preparing Active Directory for use with Logon Manager. The preparation consists of extending your Active Directory schema with Logon Manager classes and attributes, allowing Logon Manager to store credentials under respective user objects, and creating the desired tree structure. Before starting this procedure, make sure you have done the following:

1. Performed a health check on your Active Directory schema as described by Microsoft best practices.

2. Installed the Administrative Console, as described in the Enterprise Single Sign-On Suite Installation Guide.

1.7.1 Extending the Schema

1. Start the Logon Manager Administrative Console. By default, the shortcut to the console is located in Start> Programs> Oracle> Logon Manager> Logon Manager Console.

Note:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

2. In the Console, select Extend Schema from the Repository menu. The Console displays the "Connect to Repository" dialog.

3. In the Server Name field, enter a fully qualified IP address, hostname, or NetBIOS name of your schema master domain controller.

4. In the Repository Type drop-down list, select Microsoft Active Directory Server.

5. Enter the port number on which your directory is listening for connections.
The default ports are 636 for SSL connections and 389 for non-SSL connections.

6. (Optional) If you configured your domain controllers to use SSL, leave the Use secure channel (SSL) option selected; otherwise, deselect it. (See SSL Support for more information.)

7. In the Username/ID and Password fields, enter the credentials of the account you want Logon Manager to use to connect to Active Directory. Depending on your environment, you may need to include the corresponding domain name as part of the user name, e.g., ITSLIFE\Jim.

8. Click OK and wait for the Console to perform the schema extension. The Console displays a status dialog showing the progress. When the schema has been successfully extended, a confirmation message appears in the status dialog:

If the schema extension fails, see Active Directory Schema Extension Failures in Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory for troubleshooting steps.

9. Click Close.

1.7.2 Enabling the Storage of User Credentials under User Objects

When you enable the storage of user credentials under respective user objects, Logon Manager makes the following changes in the directory:

- Adds the user class as a possible superior to the vGOUserData class.

- Grants all users the right to create vGOUserData objects. These rights are granted at the directory root and are recursively inherited down to the user objects.

To enable the storage of user credentials under respective user objects:

1. In the Console, select Enable Storing Credentials Under User Object (AD Only) from the Repository menu. The Console displays a confirmation dialog informing you of the changes about to be made to your Active Directory schema.

2. Click OK and wait for the Console to make the changes. When the changes have been made, the Console displays a confirmation dialog:

3. Verify that the changes have been made successfully:

1. Open the "Active Directory Schema" snap-in in the Microsoft Management Console. If the snap-in is not present in the console, install it by following the instructions in the Microsoft Knowledge Base.

2. Expand the Classes node and navigate to the vGOUserData class.

3. Right-click the vGOUserData class and select Properties from the context menu.

4. In the "vGOUserData Properties" dialog, select the Relationship tab.

5. Check whether the user class appears in the Possible Superior field:

Note:

Members of protected groups (i.e., users whose ACLs are governed by the AdminSDHolder object) will not be able to store credentials under their user objects until the AdminSDHolder ACL is updated with permissions required by this feature. See Select Users Unable to Store Credentials Under User Objects in Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory for instructions on how to remedy this issue.

If the user class does not appear as a possible superior, see All Users Unable to Store Credentials Under User Objects in Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory for possible causes and remedial steps.

1.7.3 Creating the Configuration Object Container and Sub-Tree Structure

Note:

While it is possible to use an existing container for storing Logon Manager objects, doing so may impair directory performance. Oracle highly recommends that you create a dedicated configuration object container.

1. In the Logon Manager Administrative Console, select the Repository node in the tree in the left pane.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Repository" dialog.

3. Fill in the fields as explained in steps 3-7 on pages 26-27 and click OK to connect.

4. In the tree, right-click the desired parent container and select New Container from the context menu, as shown below:

The Console displays the "New Container" dialog:

5. In the "New Container" dialog, enter the desired name and click OK.

Note:

Note: Unless your environment calls for a specific name for this container, Oracle recommends that you use the default name, SSOConfig.

6. Repeat steps 4 and 5 to create any additional containers you may need.

1.8 Configuring the Active Directory Synchronizer

After you have prepared Active Directory for Logon Manager, you must configure the Active Directory synchronizer for your environment. Configure these settings on your "template" client machine and include them in the MSI package you will use to deploy Logon Manager to end-users. Before starting this procedure, make sure that the Logon Manager Administrative Console and the Logon Manager Agent (including the Active Directory synchronizer plug-in) are installed.

Note:

Do not include application templates in the MSI package as they will not function in a directory-synchronized environment. The ability to include templates directly in the MSI package is for specialized use only. Instead, push them to the directory for automatic retrieval by the Logon Manager Agent.

1. Launch the Logon Manager Administrative Console.

2. In the left-hand pane, right click the Global Agent Settings node, then selectImport > From Live HKLM from the context menu. The Console imports the current Agent settings from the Windows registry.

3. Configure the Agent as described in Recommended Global Agent Settings and Recommended Administrative Overrides.

Note:

When the check box next to a setting is unchecked, the default value for the setting (shown grayed-out to the right of the check box) is in effect.

4. Save your configuration to an XML file for future reference. From the File menu, select Save, enter the desired file name, and click Save. If you change your settings, you can load this XML file into the Console to revert back to your original choices.

5. From the Tools menu, select Write Global Agent Settings to HKLM. The Console writes your changes to the registry and restarts the Agent.

6. Continue to the next section to complete the configuration of Logon Manager.

1.9 Testing the Logon Manager Configuration

Once you have finished configuring your Logon Manager configuration, complete the following steps to test it and correct any errors that might prevent Logon Manager from functioning:

1. Launch the Logon Manager Administrative Console.

2. In the left-hand pane, right click the Global Agent Settings node, then selectImport > From Live HKLM from the context menu. The Console imports the current Agent settings from the Windows registry.

3. From the Tools menu, select Test Global Agent Settings.

4. Read the warning that appears and click OK to proceed:

5. The "Logon Manager Configuration Test Manager" window appears. Follow the instructions in the window to test your configuration and correct any errors. For more information on each option, select the Help (question mark) button in the upper right corner of the window.

2 Deploying Logon Manager
with Microsoft AD LDS (ADAM)

This chapter describes best practices for deploying Logon Manager with Microsoft AD LDS (ADAM). It contains the following sections:

- Logon Manager and AD LDS (ADAM) Environments

- Designing the AD LDS (ADAM) Directory Sub-Tree

- Recommended Global Agent Settings

- Recommended Administrative Overrides

- Overview of the Deployment Process

- Creating an AD LDS (ADAM) Instance

- Preparing the AD LDS (ADAM) Instance for Logon Manager

- Configuring the AD LDS (ADAM) Synchronizer

2.1 Logon Manager and AD LDS (ADAM) Environments

You have the choice to deploy Logon Manager in a directory environment, such as AD LDS (ADAM) or AD LDS, which enables the delivery of single sign-on capability to any machine on the network through central storage of application credentials, templates, and policies. Users synchronize with the directory to download these items and update their credential stores with new or changed credentials.

Adding Logon Manager to your existing directory environment provides the following benefits:

- Logon Manager leverages the existing user accounts, groups, and native directory permissions (ACLs) without the need to manage these items separately or synchronize them with another directory or database.

- Logon Manager data is automatically protected by your existing backup and disaster recovery plans.

- No dedicated servers or server-side processes are required; Logon Manager's scalability and performance depend solely on the capacity and robustness of your existing directory infrastructure.

- Administrators are not burdened with additional administrative tasks or the need to learn new tools or concepts. Delegated administration of Logon Manager is achieved through the native capabilities of the directory.

A directory also enables the organization of Logon Manager templates and policies into a highly visual hierarchy. While you can use a flat model if your environment calls for it, a properly set-up hierarchy can help maintain top directory, Agent, and network performance, as well as simplify Logon Manager administration by permitting more efficient access control.

2.1.1 Benefits of AD LDS (ADAM)-Based Deployments

AD LDS (ADAM) provides data storage and retrieval for directory-enabled applications, without the dependencies that are required by Active Directory. AD LDS (ADAM) provides much of the same functionality as Active Directory, but it does not require the deployment of domains or domain controllers, and the directory schema for AD LDS (ADAM) is completely independent of the enterprise schema you may be using in an Active Directory domain. You can run multiple instances of AD LDS (ADAM) concurrently on a single server, with an independently managed schema for each AD LDS (ADAM) instance. The following are the benefits of deploying Logon Manager with AD LDS (ADAM):

- Ideal for pilot and proof-of-concept deployments. A fully functional AD LDS (ADAM) instance that very closely mimics a full-scale Active Directory environment can be set up in minutes and is entirely self-contained (requiring only the Active Directory host on which it runs).

- Simplified deployment. AD LDS (ADAM) is available free of charge from Microsoft. Deployment within existing Active Directory environments is easy and allows the reuse of existing user accounts and groups.

- Efficient scaling and fault tolerance. Since AD LDS (ADAM) is based on Active Directory code, its scalability characteristics are similar to those of Active Directory. Just two servers, capable of supporting approximately 5,000 Logon Manager users, are enough to ensure basic fault tolerance. If your organization consists of more than 5,000 members, consult a Microsoft expert for more information on scalability and fault tolerance.

Additionally, deploying Logon Manager with AD LDS (ADAM) in an existing Active Directory environment provides the following benefits:

- Retraining is minimized. Administrative procedures for AD LDS (ADAM) are very similar to those for Active Directory. Administrators skilled with Active Directory will be able to deploy and maintain AD LDS (ADAM) instances with little additional effort; management tools for both platforms mirror management tools for Active Directory.

- Existing Active Directory accounts and policies can be leveraged. Active Directory user accounts, groups, and policies are instantly available in AD LDS (ADAM). You do not need to import, re-create or synchronize your existing configuration and user account data.

2.1.2 Active Directory vs. AD LDS (ADAM)

The table below highlights the key differences between Active Directory and AD LDS (ADAM):

Feature

Active Directory

AD LDS (ADAM)

Server Discovery and Failover

Fully automatic. Client broadcasts request and listens for reply from the nearest server. Failover is simplified as fallback from server to server is automatic.

Automatic when using a load balancer; otherwise requires an explicit server list.

For the benefits of load balancing, see Benefits of Load-Balancing an Logon Manager Deployment. If not using a load balancer, client must be explicitly provided with a list of servers to connect to, ordered by geographic proximity.

Schema Extension

Global. You must perform a schema extension to add the required Logon Manager object classes to your Active Directory schema. Existing classes and attributes are not modified in any way. Administrators must understand the impact (usually negligible) of the extension on the directory as a whole. Detailed information on the schema extension is available in Appendix B: Logon Manager Repository Object Classes and Attributes.

Local. When deploying Logon Manager on AD LDS (ADAM), you must perform a schema extension against the target AD LDS (ADAM) instance only. The extension consists of the same four object classes as the Active Directory schema extension.

Credential Storage Under User Objects

Yes. You have the option to store Logon Manager application credentials under respective user objects.

No. All user credentials are stored under a dedicated OU within the AD LDS (ADAM) instance. This OU contains an object for each Logon Manager user.

Usage Reporting

Yes. When Logon Manager is deployed on Active Directory, you can obtain point-in-time information on user credentials stored in the directory.

No. AD LDS (ADAM) environments do not support point-in-time information reporting for Logon Manager. (Available on AD LDS (ADAM) when Provisioning Gateway is installed.)

For more in-depth information about AD LDS (ADAM) and its applications, please see:

- ADAM FAQ: http://www.microsoft.com/windowsserver2003/ADAM/ADAMfaq.mspx

- AD LDS FAQ: http://technet.microsoft.com/en-us/library/cc755080%28WS.10%29.aspx

2.1.3 How Logon Manager Extends the AD LDS (ADAM) Schema

Before Logon Manager can store data in AD LDS (ADAM), you must extend the schema of the selected AD LDS (ADAM) instance (the Active Directory host's schema is not affected) using the Administrative Console. The schema extension consists of adding four object classes and setting the appropriate permissions so that objects of those types can be created, read, modified, and deleted. Existing classes and attributes are not modified in any way.

Note:

Schema extension is a post-installation procedure. For instructions, see Preparing the AD LDS (ADAM) Instance for Logon Manager. Oracle highly recommends that you perform a schema health check (as described by Microsoft best practices) before performing the schema extension.

For detailed information on the schema extensions made by Logon Manager, see the following appendices:

- Appendix A: Minimum Administrative Rights for Logon Manager Repository Objects

- Appendix B: Logon Manager Repository Object Classes and Attributes

2.1.4 How Logon Manager Synchronizes with AD LDS (ADAM)

The Logon Manager Agent uses the AD LDS (ADAM) synchronizer plug-in to communicate with AD LDS (ADAM). When properly configured, synchronization occurs whenever one of the following events takes place:

- The Logon Manager Agent starts

- Application credentials are added, modified, or deleted by the end-user

- The machine running the Agent acquires an IP address or its existing IP address changes (if Logon Manager is configured to respond to these events)

- The auto-synchronize interval elapses (if configured)

- The user initiates synchronization via the Agent's "Refresh" function

During synchronization, the Logon Manager Agent traverses the Logon Manager sub-tree and loads the contents of the sub-containers to which the current user has been granted access; it also synchronizes any credentials that have been added, modified, or deleted since the last synchronization.

2.1.5 How Logon Manager Handles and Stores Application Credentials

Logon Manager encrypts application credentials using a unique key generated when the user completes the First-Time Use (FTU) wizard. The credentials remain encrypted at all times, including in the Agent's local cache, the directory, and while in transit over the network. Logon Manager only decrypts credentials (to memory, never to disk) when a configured application requests logon, and wipes the target memory location as soon as the logon request completes. The amount of data Logon Manager stores per enabled application and per user is trivial (measurable in bytes and small kilobytes).

2.1.6 Benefits of Load-Balancing an Logon Manager Deployment

When a directory server fails, Logon Manager will attempt to contact the next one on its server list. If no servers on the list can be reached, synchronization becomes unavailable until the problem is remedied. If your environment calls for more than one physical AD LDS (ADAM) server, Oracle highly recommends using a load balancer that will evenly and automatically distribute the requests coming from the network among the AD LDS (ADAM) servers behind it. If a server goes offline, the rest can temporarily absorb the workload of the failed machine, providing failover transparency to the end-user and adequate time to bring the faulty server back online.

2.1.7 Further Reading

An in-depth discussion of the Logon Manager software architecture is beyond the scope of this guide. To obtain Oracle white papers containing additional information, contact your Oracle representative.

2.2 Designing the AD LDS (ADAM) Directory Sub-Tree

Logon Manager gives you the freedom to set up the directory structure to best fit the needs of your organization. Specifically, you have the choice to store your data in a flat model, or create a hierarchy. While a flat model works fine for small deployments, growing and large deployments should utilize a hierarchy from the very beginning. The exact structure of your sub-tree will depend on the following factors:

- Number of users

- Number of applications that Logon Manager will support

- Robustness of the existing infrastructure

- Structure of your organization.

2.2.1 Guidelines for Structuring the AD LDS (ADAM) Sub-Tree for Logon Manager

Oracle recommends that you set up your sub-tree as a hierarchy by following the guidelines below:

- Use OUs to group templates, policies, and credentials by category, such as department or division, according to the structure of your organization.

- Control access at the OU level.

- Disable inheritance and grant no user rights at the Logon Manager root container, unless your environment dictates otherwise.

When set up this way, a hierarchy provides the following benefits:

- Highly visual and self-documenting tree structure. When you view your sub-tree in a directory browser, the sub-tree structure is self-descriptive and easy to follow.

- No unwanted inheritance of rights. Users will not natively inherit rights to sub-OUs that you do not want them to access. This eliminates the need to explicitly deny unwanted access rights that are being passed down the tree.

- Robust network, Agent, and directory performance. Typically, users who download large numbers of templates and policies generate more network traffic and a higher load on the directory than users who only download items relevant to their jobs. Grouping conserves your environment's resources and improves Agent response time.

- Distributed administrative tasks. Your templates are organized into easily controllable sets, and access rights determine who can manage which templates. You also have the ability to implement rights-based version control of your templates.

- Low administrative overhead. Controlling access at the template level requires setting permissions for each individual template via the Logon Manager Administrative Console; controlling access at the OU level is achieved via delegated administration using Microsoft and third-party management tools.

The following figure depicts a sample Logon Manager sub-tree whose design reflects the above best practices.

In our sample scenario, users from the Portland division do not need access to applications used by the Sacramento division, and vice versa; therefore, each division's templates and policies live in dedicated sub-OUs under the root and one division cannot access another division's sub-OU. In the end, your environment will dictate the specifics of your implementation.

Note:

Oracle highly recommends that you store templates, policies, and application credentials in individual OUs. To do this, you must Use Configuration Objects.

Unlike Active Directory, AD LDS (ADAM) does not permit Logon Manager to store application credentials under user objects. Instead, when deployed on AD LDS (ADAM), Logon Manager stores application credentials in a flat format inside a special OU called People. The People container, by default, resides in the root of your AD LDS (ADAM) partition; however, if you require more granular access control, you can create multiple People containers (each must have a unique path) for different departments or regions within your organization, just like you would for templates and policies, as shown in Figure 3. You would then configure each department's Logon Manger instances to seek application credentials in that department's People OU. You must create the People OU and provide its full path to the AD LDS (ADAM) synchronizer as described in Creating the People OU.

Note:

A container object is automatically created inside the People OU at first use for each Logon Manager user in order to keep user data private and separate.

If you are using Provisioning Gateway and want to take advantage of multiple People OUs, the following limitations apply:

Note:

It is not possible to use multiple People OUs with Provisioning Gateway with a single domain.

- The People OU must reside inside a parent container at the root of the AD LDS (ADAM) partition,

- The parent container's name must be the name of the domain (NT-style) of the users whose application credentials are stored in the corresponding People OU. If necessary, create a separate domain for each department or region that requires a separate People OU and move the corresponding users to that domain.

If you are starting out with a flat model, but expect the number of users and provisioned applications to grow, create a sub-container under the root and use it to store your templates and policies as a flat file until you are ready to transition to a hierarchy. Monitor the performance of your environment as you add more users and provision more applications, and transition to a hierarchy sooner rather than later to minimize the required effort. When transitioning to a hierarchy, use the existing container as your new Logon Manager root container and create sub-OUs underneath it.

2.2.2 Version Control and Pre-Flight Testing of Templates and Policies

Oracle recommends that you create dedicated sub-OUs for each stage of your workflow: development, staging, and production, as shown in Figure 3. This way you will be able to:

- Track changes made to templates and policies as they pass through the workflow and enter production by keeping shadow copies each time templates and policies move from one workflow stage to the next.

- Roll back to a previous version of a template or policy if need arises.

- Control who can work on which templates and policies at each workflow stage. In particular, you should strictly enforce rules governing who can put a template or a policy into production.

Always test every application template and administrative override in a contained environment before you deploy it to end-users. Testing helps you stage your changes and resolve any potential issues that would be much more costly to resolve were they to occur in production. Testing is particularly critical in large deployments: if you push out a misconfigured template or an incorrect administrative override network-wide, access to mission-critical applications may be lost enterprise-wide.

When setting up a contained test environment, create a dedicated test container to which only members of your development group will have access. Then, point the test Logon Manager Agent(s) at this container and place your templates and administrative overrides in it. Once you confirm that the templates and policies are functioning as intended, move them to the target production container.

If you decide not to keep shadow copies of your templates after you test them, move them from the test container to target production containers as follows:

1. Retrieve the template from the directory.

2. Create a local backup of the template.

3. Push the duplicate into the new location within the directory.

4. Delete the template from its original location.

2.2.3 Precautions for Configuring Object Access Control Lists Using the Console

When you modify an object's Access Control List (ACL) using the Console, the connection string (repository host name or IP) used to connect to the repository is treated by the Console as a unique repository identifier and recorded in the object. The Console is thus unable to distinguish between two unique repositories and two methods to connect to the same repository.

Because of this, if you use different connection strings for the same repository, e.g. an IP address and host name, the changes made to an object from one session to the next will be lost. To work around this issue in an AD LDS (ADAM) environment, always use the same connection string (IP address or host name) when modifying object ACLs through the Console.

2.2.4 Precautions for Upgrading the Agent and Console

To maintain template and settings compatibility throughout your environment, you should always use a version of the Console matching the oldest version of the Agent still deployed in production. Due to template schema changes between releases, older Agents may exhibit unexpected behavior when supplied a template created or modified by a newer version of the Console. For this reason, if you are upgrading to a newer release of Logon Manager, Oracle highly recommends that you do not upgrade your Console until all deployed Agent installations have been upgraded.

Note:

Even if you do not make any changes to a template, it is still rewritten using the currently installed Console's data schema when you push the template back to the repository.

2.3 Global Agent Settings vs. Administrative Overrides

The behavior of the Logon Manager Agent, including its interaction with the directory, is governed by settings configured and deployed to the end-user machine by the Logon Manager administrator using the Logon Manager Administrative Console. The settings fall into one of the following categories:

- Global Agent settings are the "local policy" for the Agent; they are stored in the Windows registry on the end-user machine and are included in the Logon Manager MSI package to provide the Agent with an initial configuration during deployment. Global Agent settings are stored in HKEY_LOCAL_MACHINE\Software\Passlogix (32-bit systems) or HKEY_LOCAL_MACHINE\Wow6432Node\Software\Passlogix (64-bit systems).

Caution:

Users able to modify the HKLM hive can alter their global Agent settings and thus change the behavior of the Agent from the one originally intended. To ensure that a setting will not be changed by the end-user, deploy it through an administrative override.

- Administrative overrides take precedence over the global Agent settings stored in the Windows registry and constitute the "domain" policy for the Agent. Overrides are downloaded from the central repository by the Agent during synchronization and stored in the Agent's encrypted and tamper-proof local cache, which makes them immune to end-user alterations. When role/group security is enabled, administrative overrides can be applied on a per-user or per-group basis; they can also be applied enterprise-wide to enforce configuration consistency for all users.

Note:

Be conservative when planning your administrative overrides. Fewer overrides mean less data to store and transfer, and thus more efficient synchronization with the central repository. Reducing the number of overrides also simplifies troubleshooting by eliminating unknowns, as administrative overrides cannot be viewed on the end-user machine.

Global Agent settings together with administrative overrides constitute the complete configuration policy for the Agent. The rest of this guide describes the recommended optimal configuration and complements the information found in the other Enterprise Single Sign-On Suite Administrator's Guide.

WARNING:

Settings such as domain names and user object paths should always be thoroughly tested before deployment and not deployed as administrative overrides unless absolutely necessary. A simple mistake, such as a mistyped domain name, can render end-user workstations unable to synchronize with the directory, in which case you will not be able to propagate a correction through the Console - changes will have to be made to user machines using other tools.

The figure below depicts a typical view of the Logon Manager Administrative Console set up for synchronization with AD LDS (ADAM).

The next section describes best practices for configuring Logon Manager for synchronization with AD LDS (ADAM). If you need additional information on settings described in this guide, see the online help included with the Console.

Note:

Before you begin, make sure that the Logon Manager Agent and the AD LDS (ADAM) synchronizer plug-in are installed on your machine; otherwise, AD LDS (ADAM)-related settings will not be displayed in the Console. For installation instructions, see the installation guide for your version of Logon Manager.

Tip:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

The best practice for settings not described in this and other guides is to leave them at their default values, unless your environment dictates otherwise. The default value is automatically in effect whenever the check box for the setting in the Administrative Console is not checked. The value is visible in the inactive field next to the check box.

2.4 Recommended Global Agent Settings

This section lists Oracle-recommended best-practice global Agent settings. Configure the settings as described below and include them in the customized Logon Manager MSI package. For instructions on creating the package, see the "Packaging Logon Manager for Mass Deployment" section in the guide Enterprise Single Sign-On Suite Installation Guide.

2.4.1 Use Configuration Objects

On AD LDS (ADAM) deployments Oracle highly recommends that you use directory objects for storing user and configuration data, allowing hierarchical storage, as well as role/group-based access control for individual containers, templates, and policies as described in Designing the AD LDS (ADAM) Directory Sub-Tree. If you disable this feature, Logon Manager will store all template and configuration data as a single flat file under the tree root.

Located in: Global Agent Settings > Live > Synchronization

To enable: Select the check box, then select Yes from the drop-down list.

2.4.2 Configure a Server List with Desired Failover Order

In AD LDS (ADAM) environments, server URLs must be explicitly provided to Logon Manager. Oracle highly recommends using at least two physical AD LDS (ADAM) servers and placing them behind a load balancer for automatic, transparent failover. If you choose not to use a load balancer, arrange the server URLs in order of geographic proximity to the end-user so that the performance hit due to physical distance between the end-user and the next available server is minimized. For more information on load balancing, see Benefits of Load-Balancing an Logon Manager Deployment.

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To set: Select the check box, click the (…) button, and enter the desired values (one per line) as shown below. When you are finished, click OK.

2.4.3 Specify the Path to the Logon Manager Configuration Objects

You must specify the location of the Logon Manager root container (which stores Logon Manager configuration objects) for Logon Manager to store data in AD LDS (ADAM).

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To set: Select the check box, click the (…) button, and enter the desired value. When you are finished, click OK.

2.4.4 SSL Support

Logon Manager repository synchronizers ship with SSL support enabled and Oracle highly recommends that you do not disable it. Your environment should always utilize SSL for all connections to the Logon Manager and other repositories for maximum security.

Note:

Note: You must configure your domain controllers to use SSL before deploying Logon Manager. For instructions, see the following MSDN article: http://msdn.microsoft.com/en-us/library/aa364671(VS.85).aspx

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To re-enable (if disabled): Deselect the check box.

2.4.5 Select the Credentials to Use when Authenticating to the Repository

Use the Credentials to use option to select the credentials Logon Manager should use when authenticating to the repository. Oracle recommends that you set this to Local computer credentials so that the user will not be prompted to reauthenticate if Logon Manager is unable to authenticate to the repository.

Note:

Do not leave this at the default setting, Try local computer credentials before using AD LDS (ADAM) server account. Doing so will cause an authentication failure (and the re-authentication prompt to appear, unless disabled) if the repository and the end-user machine are not part of the same domain.

If you are using Smart Cards to authenticate to Logon Manager, you can also use the card's certificate to authenticate to the repository by selecting Use card's certificate from the drop-down menu. For more information, see the Oracle Enterprise Single Sign-On Suite Plus Administrator's Guide.

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To set: Select the check box, then select the appropriate option from the drop-down list.

2.4.6 Configure Logon Manager to Use a Specific People OU

If you created a People OU in a location other than default (root of the AD LDS (ADAM) partition), or you have created multiple People OUs for more granular control of access to application credentials, you must configure the target Logon Manager instances to use the corresponding People OUs, as explained in Designing the AD LDS (ADAM) Directory Sub-Tree.

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To set: select the check box next to the People container option and enter the fully qualified path to the specific People OU you want Logon Manager to use into the field. For example:

OU=People,OU=City,OU=State,OU=Country,OU=ssopartition,DC=company,DC=com

2.4.7 Choose Whether to Prompt the User when Disconnected from the Repository

Use the Prompt when disconnected option to decide whether Logon Manager should prompt the user to re-authenticate to the repository upon authentication failure or disconnection. Oracle recommends that you set this to No; doing so will avoid unnecessary confusion and helpdesk calls.

Located in: Global Agent Settings > Live > Synchronization > ADAMSyncExt

To set: Select the check box, then select the appropriate option from the drop-down list.

This option is directly related to the Credentials to use option described above and has no effect if Allow disconnected operation is set to No.

2.4.8 Add the AD LDS (ADAM) Synchronizer to the Synchronizer Order List

Ensure that the AD LDS (ADAM) (ADAMSyncExt) synchronizer plug-in is present and enabled in the Synchronizer order list if at least one of the following is true for your environment:

- Logon Manager is synchronizing with more than one repository,

- Logon Manager is using roaming synchronization,

- Kiosk Manager is installed in your environment.

Note:

Instructions for configuring Logon Manager for multi-repository and roaming synchronization, as well as installing and configuring Kiosk Manager, are beyond the scope of this guide. For more information, see the documentation for your version of Logon Manager and/or Kiosk Manager.

Located in: Global Agent Settings > Synchronization

To set: Select the check box, then click the (…) button. In the list that appears, select the checkbox next to ADAMSyncExt and click OK. Use the up/down arrows to set synchronization order as necessary.

2.4.9 Make the Logon Manager Agent Wait for Synchronization on Startup

To ensure that users always have the most recent credentials, application templates, password policies, and administrative overrides, configure the Agent to wait for synchronization on startup. When this option is enabled, the Agent checks whether the directory is online. If the directory is online, the Agent does not respond to application logon requests until it successfully synchronizes with the directory. If the directory is offline, the Agent does not attempt to synchronize and starts immediately.

Located in: Global Agent Settings > Live > Synchronization

Use the default value (Yes) unless your environment requires otherwise.

2.4.10 Use Optimized Synchronization

Optimized synchronization instructs the Logon Manager Agent to synchronize only credentials that have changed since the last synchronization. Do one of the following, depending on your environment:

- Enable this option to improve synchronization performance on deployments with large numbers of credentials per user.

- Disable this option to improve synchronization performance on deployments with fewer than five credentials per user and a large number of templates downloaded per user.

Located in: Global Agent Settings > Live > Synchronization

Use the default value (Yes) unless your environment requires otherwise.

2.4.11 Restrict Disconnected Operation

During deployment, configure the Logon Manager Agent not to run if a connection to the directory cannot be established. This will prevent users from completing the First-Time Use (FTU) wizard when the Agent is not connected to the directory and no local cache is present. By not allowing the Agent to run when the directory is not available, you avoid a common situation in which a second set of encryption keys is created when a user completes the FTU wizard while disconnected from the directory.

Note:

See the guide Logon Manager Best Practices: Configuring the Logon Manager Agent for more information on this required best practice.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then select No from the drop-down list.

2.5 Recommended Administrative Overrides

Directory synchronization settings, such as domain names and object paths, should not be deployed as administrative overrides. (See Global Agent Settings vs. Administrative Overrides for an explanation.) The recommended best-practice overrides are described in the section "Configuring Logon Manager" in the guide Logon Enterprise Single Sign-On Suite Administrator's Guide.

2.6 Overview of the Deployment Process

This section provides a brief high-level overview of the Logon Manager deployment process on AD LDS (ADAM). Make sure you have read all of the preceding sections of this document before proceeding with deployment. Deploying Logon Manager with MS AD LDS (ADAM) requires you to:

1. 1. Obtain the following documents:

- The latest version of this document

- Oracle Enterprise Single Sign-On Suite Installation Guide

- Oracle Enterprise Single Sign-On Suite Administrator's Guide

2. If you have not already done so, install AD LDS (ADAM) on the target server. The AD LDS (ADAM) installer and installation instructions are available on the Microsoft Web site.

3. Create groups for Logon Manager administrators and Logon Manager users. Basic instructions are provided in Appendix E: Creating the Required User Groups on AD LDS (ADAM).

4. Create a new AD LDS (ADAM) instance that will be used by Logon Manager, as described in Creating an AD LDS (ADAM) Instance.

5. Install the Logon Manager Agent and the Logon Manager Administrative Console on a machine within your domain, as described in the installation guide for your version of Logon Manager. Make sure you select the AD LDS (ADAM) Synchronizer when installing the Agent.

6. Complete the steps in Preparing the AD LDS (ADAM) Instance for Logon Manager:

1. Extend the AD LDS (ADAM) instance schema with Logon Manager classes and attributes.

2. Create the People OU, which will store each user's application credentials.

3. Create the Logon Manager configuration object container and desired tree structure.

4. Grant the required permissions.

7. Configure Logon Manager as follows:

1. Complete the steps in Configuring the AD LDS (ADAM) Synchronizer.

2. Configure the options described in Recommended Global Agent Settings in this guide.

3. Configure the options described in the "Configuring the Logon Manager Agent" section of the Enterprise Single Sign-On Suite Administrator's Guide.

Note:

For detailed descriptions of the settings in question, see the Console's online help.

8. On a test machine, do the following:

- Create a pilot set of core templates and policies.

- Finalize the end-user experience by testing each core template, global Agent setting, and administrative override that will be deployed into production.

9. Create a custom MSI package and deploy it to end-user machines by completing the steps in the "Packaging Oracle Enterprise Single Sign-On Suite for Mass Deployment" section of the Oracle Enterprise Single Sign-On Suite Installation Guide.

10. Create, test, and deploy the remaining application templates. See the guide Configuring and Diagnosing Application Templates for in-depth information on provisioning different types of applications.

2.7 Creating an AD LDS (ADAM) Instance

This section describes how to create an AD LDS (ADAM) instance on which you will deploy Logon Manager. If you have not already done so, install AD LDS (ADAM) on the target server. The AD LDS (ADAM) installer and installation instructions are available on the Microsoft web site. Before you begin, note the following:

- Oracle recommends deploying on Windows Server 2008 and later versions of the Windows Server operating system family. Deployment on Windows XP or Windows 7 is discouraged. Deployment on Windows Server versions prior to 2008 is not supported.

- To simplify deployment, Oracle highly recommends creating an AD LDS (ADAM) instance that runs on the default port (636 for SSL connections; non-SSL connections to AD LDS (ADAM) are supported but not recommended). If you use a custom port, it must be open between all clients and the target servers.

Note:

Regardless of the type of connection to the repository, user credential data remains encrypted at all times.

- If you are installing AD LDS (ADAM) on a domain controller or another server on which a directory is already running, you will not be able to use the default ports; therefore, Oracle highly recommends deploying Logon Manager on a member server instead of a domain controller.

To create the target AD LDS (ADAM) instance:

Note:

The AD LDS (ADAM) setup wizard screens depicted in this guide may differ visually across the supported versions of the Windows Server operating system family; however, the procedure is identical for all supported versions.

1. Launch the AD LDS (ADAM) Setup Wizard.

- On Windows Server 2008: Click Start > Programs> Administrative Tools> Active Directory Lightweight Directory Services Setup Wizard.

- On Windows Server 2008 R2:

Note:

: Make sure you have added the "Active Directory Lightweight Directory Services" role to your server before starting this procedure.

In Server Manager, expand the Roles node and select the Active Directory Lightweight Directory Services role. In the right-hand pane, expand the Advanced Tools>AD LDS Tools section and click AD LDS Setup Wizard.

2. In the "Welcome" screen, click Next.

3. In the "Setup Options" screen, select A unique instance and click Next.

4. Name your AD LDS (ADAM) instance and click Next. The recommended name is ssopartition.

5. Enter the desired port numbers for this AD LDS (ADAM) instance. If you are not using the default ports (389/636), note the custom port numbers you enter here - you will need them later to configure Logon Manager.

6. Select Yes, create an application directory partition and give the partition a fully-qualified DN. This is the root of your AD LDS (ADAM) instance's sub-tree. The DN must start with ou= and not cn= as the dialog box suggests; otherwise, the Logon Manager deployment will fail.

8. Specify the locations in which you want AD LDS (ADAM) to store its files. In most cases, it is safe to accept the default values.

9. Specify the privileges that this instance of AD LDS (ADAM) will use to run.

10. Select This Account, then click Browse to specify a user or group you want to have administrative privileges for this instance of AD LDS (ADAM). To prevent lockout from your entire Logon Manager deployment, Oracle highly recommends creating a dedicated group that contains two or more users with administrative privileges over the target AD LDS (ADAM) instance. For more information, see Appendix E: Creating the Required User Groups on AD LDS (ADAM).

11. Select Do not import LDIF files for this instance of AD LDS (ADAM) and click Next.

12. In the summary screen, review your configuration choices. If you need to make changes, click Back; otherwise, click Next and wait for AD LDS (ADAM) to create the instance.

13. When the process is complete, click Finish to quit the wizard.

2.8 Preparing the AD LDS (ADAM) Instance for Logon Manager

This section describes the basic procedures for preparing AD LDS (ADAM) for use with Logon Manager. The preparation consists of extending your AD LDS (ADAM) schema with Logon Manager classes and attributes, allowing Logon Manager to store credentials under respective user objects, and creating the desired tree structure. Before starting this procedure, make sure that you have installed the Administrative Console.

2.8.1 Extending the Schema

1. Start the Logon Manager Administrative Console. By default, the shortcut to the console is located in Start> Programs> Oracle> ESSO Suite Administrative Console.

Note:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

2. In the Console, select Extend Schema from the Repository menu. The Console displays the "Connect to Repository" dialog.

3. In the Server Name field, enter a fully qualified IP address, hostname, or NetBIOS name of your schema master domain controller.

4. In the Repository Type drop-down list, select Microsoft AD LDS (ADAM).

5. Enter the port number on which your directory is listening for connections. The default port is 636 for SSL connections and 389 for non-SSL connections.

6. (Optional) If you configured your domain controllers to use SSL, leave the Use secure channel (SSL) option selected; otherwise, deselect it. (See SSL Support for more information.)

7. In the Username/ID and Password fields, enter the credentials of the account you want Logon Manager to use to connect to AD LDS (ADAM). Depending on your environment, you may need to include the corresponding domain name as part of the user name, for example DOMAIN\user.

8. Click OK and wait for the Console to perform the schema extension. The Console displays a status dialog showing the progress. When the schema has been successfully extended, a confirmation message appears in the status dialog:

9. Click Close.

If the schema extension fails, check to make sure you have specified the AD LDS (ADAM) instance DN correctly, as described in step 6 on page 28. If the DN is incorrect, delete and re-create the AD LDS (ADAM) instance, then repeat this procedure.

2.8.2 Creating the People OU

After extending the AD LDS (ADAM) instance schema, you must create at least one People OU, which Logon Manager will use to store application credentials. By default, Logon Manager expects the People OU to reside at the root of the target AD LDS (ADAM) partition.

However, if you desire more granular control, you can create one or more People OUs anywhere in the directory and provide different instances of Logon Manager with the fully qualified paths to different People OUs, based on the requirements of your organization, as described in Configure Logon Manager to Use a Specific People OU.

To create the People OU:

1. In the ESSO Suite Administrative Console, select the Repository node in the tree.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Repository" dialog. Fill in the fields as explained in steps 3-7 on page 54 and click OK to connect.

3. In the tree, right-click the root of the target AD LDS (ADAM) instance, and selectCreate People Container from the context menu.

4. Verify that the People OU now exists at the root of the AD LDS (ADAM) instance's sub-tree.

If the People OU does not appear after you complete the above steps, or if you receive errors indicating naming violations or other problems in the directory, consult the AD LDS (ADAM) documentation for possible causes and remedies.

2.8.3 Creating the Configuration Object Container and Sub-Tree Structure

Note:

While it is possible to use an existing container for storing Logon Manager objects, doing so may impair directory performance. Oracle highly recommends that you create a dedicated configuration object container.

1. In the Logon Manager Administrative Console, select the Repository node in the tree.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Directory" dialog.

3. Fill in the fields as explained in steps 3-7 on page 32 and click OK to connect.

4. In the tree, right-click the desired parent container and select New Container from the context menu, as shown below:

The Console displays the "New Container" dialog:

5. In the "New Container" dialog, enter the desired name and click OK.

Note:

Unless your environment calls for a specific name for this container, Oracle recommends that you use the default name, SSOConfig.

6. Repeat steps 4 and 5 to create any additional containers you may need.

2.8.4 Granting Required Permissions to Logon Manager Users

You must grant Logon Manager users the following permissions in order to enable them to use Logon Manager:

- Read access to the Logon Manager application partition. This permits users to read configuration objects and credentials during synchronization.

- Write access to thePeople OU. This permits users to create credential objects during synchronization.

Note:

This procedure assumes you have already created the SSOUsers group and added the desired users to the group. You will grant the permissions listed above to the SSOUsers group, not individual users. For instructions on creating the group and assigning users to the group, see Appendix B: Logon Manager Repository Object Classes and Attributes.

To grant these permissions:

1. Log on to the target server as an administrator and open a command prompt.

2. Use the following command to grant the SSOUsers group read access to the Logon Manager application partition (note that the command is a single line):
dsacls \\<hostname>:<port>\ <sso_partition_dn> /G "<domain>\SSOUsers":gr

3. Use the following command to grant the SSOUsers group write access to the People OU (note that the command is a single line):
dsacls \\<hostname>:<port>\ OU=People,<sso_partition_dn> /G "<domain>\SSOUsers":CCWS

Substitute the variables in the above commands as follows:

- <hostname> - the URL of the server running the target AD LDS (ADAM) instance.

- <domain> - target domain name.

- <port> - the port on which the target AD LDS (ADAM) instance is listening for connections.

- <sso_partition_dn> - the fully qualified DN of the Logon Manager application partition. Example: ou=ssopartition,dc=ssolab,dc=com

2.9 Configuring the AD LDS (ADAM) Synchronizer

After you have prepared AD LDS (ADAM) for Logon Manager, you must configure the AD LDS (ADAM) synchronizer for your environment. Configure these settings on your "template" client machine and include them in the MSI package you will use to deploy Logon Manager to end-users. Before starting this procedure, make sure that the Logon Manager Administrative Console and the Logon Manager Agent (including the AD LDS (ADAM) synchronizer plug-in) are installed.

Note:

Do not include application templates in the MSI package as they will not function in a directory-synchronized environment. The ability to include templates directly in the MSI package is for specialized use only. Instead, push them to the directory for automatic retrieval by the Logon Manager Agent.

1. Launch the Logon Manager Administrative Console.

2. In the left-hand pane, right click the Global Agent Settings node, then selectImport > From Live HKLM from the context menu. The Console imports the current Agent settings from the Windows registry.

3. Configure the Agent as described in Recommended Global Agent Settings and Recommended Administrative Overrides.

Note:

When the check box next to a setting is unchecked, the default value for the setting (shown grayed-out to the right of the check box) is in effect.

4. Save your configuration to an XML file for future reference. From the File menu, select Save, enter the desired file name, and click Save. If you change your settings, you can load this XML file into the Console to revert back to your original choices.

5. From the Tools menu, select Write Global Agent Settings to HKLM. The Console writes your changes to the registry and restarts the Agent.

3 Deploying Logon Manager with an LDAP Directory

Oracle Enterprise Single Sign-On Logon Manager is a secure and easily deployable single sign-on solution that acts as a middle layer between the user and the target applications. Users need to authenticate only once; Logon Manager automatically detects and handles all subsequent requests for user credentials. For more information on Logon Manager, see the Oracle Enterprise Single Sign-On Suite Technical Overview white paper available from Oracle Support.

3.1 Logon Manager and LDAP Environments

You have the choice to deploy Logon Manager in a directory environment, which enables the delivery of single sign-on capability to any machine on the network through central storage of application credentials, templates, and policies. Users synchronize with the directory to download these items and update their credential stores with new or changed usernames and passwords.

Adding Logon Manager to your existing directory environment provides the following benefits:

- Logon Manager leverages the existing user accounts, groups, and native directory permissions (ACLs) without the need to manage these items separately or synchronize them with another directory or database.

- ogon Manager data is automatically protected by your existing backup and disaster recovery plans.

- No dedicated servers or server-side processes are required; Logon Manager's scalability and performance depend solely on the capacity and robustness of your existing directory infrastructure.

- Administrators are not burdened with additional administrative tasks or the need to learn new tools or concepts. Delegated administration of Logon Manager is achieved through the native capabilities of the directory.

A directory also enables the organization of Logon Manager templates and policies into a highly visual hierarchy. While you can use a flat model if your environment calls for it, a properly set-up hierarchy can help maintain top directory, Agent, and network performance, as well as simplify Logon Manager administration by permitting more efficient access control.

Note:

To deploy Logon Manager with Oracle Identity Manager, you must enable the "Anonymous Bind" option in Oracle Identity Manager; Logon Manager will not bind to Oracle Identity Manager when "Anonymous Bind" is disabled.

3.1.1 How Logon Manager Extends Your Directory Schema

Before Logon Manager can store data in your directory, you must extend your directory schema using the Administrative Console. The schema extension consists of adding four object classes and setting the appropriate permissions so that objects of those types can be created, read, modified, and deleted. Existing classes and attributes are not modified in any way.

Note:

Note: Schema extension is a post-installation procedure. For instructions, see Extending the Schema. Oracle highly recommends that you perform a schema health check (as described by Microsoft best practices) before performing the schema extension.

For detailed information on the schema extensions made by Logon Manager, see the following appendices:

- Appendix A: Minimum Administrative Rights for Logon Manager Repository Objects

- Appendix B: Logon Manager Repository Object Classes and Attributes

3.1.2 How Logon Manager Synchronizes with Your Directory

The Logon Manager Agent uses the LDAP synchronizer plug-in to communicate with your LDAP directory. When properly configured, synchronization occurs whenever one of the following events takes place:

- The Logon Manager Agent starts.

- Application credentials are added, modified, or deleted by the end-user.

- The machine running the Agent acquires an IP address or its existing IP address changes (if Logon Manager is configured to respond to these events).

- The auto-synchronize interval elapses (if configured).

- The user initiates synchronization via the Agent's "Refresh" function.

During synchronization, the Logon ManagerAgent traverses the Logon Manager sub-tree and loads the contents of the sub-containers to which the current user has been granted access; it also synchronizes any credentials that have been added, modified, or deleted since the last synchronization.

Note:

Since Logon Manager does not support server autolocation nor use Windows credentials when authenticating to an LDAP directory other than Active Directory or AD LDS (ADAM), end-users will be prompted to authenticate to the directory in addition to authenticating to Windows and Logon Manager. In certain scenarios, it is possible to eliminate this extra prompt. See Selecting and Configuring an Authenticator for more information.

3.1.3 Benefits of Load-Balancing a Logon Manager Deployment

When a directory server fails, Logon Manager will attempt to contact the next one on its server list. If no servers on the list can be reached, synchronization becomes unavailable until the problem is remedied. If your environment calls for more than one physical directory server, Oracle highly recommends using a load balancer that will evenly and automatically distribute the requests coming from the network among the servers behind it. If a machine goes offline, the rest can temporarily absorb its workload, providing failover transparency to the end-user and adequate time to bring the faulty machine back online.

WARNING:

Deploying Logon Manager with multiple LDAP servers that use replication for synchronization behind a load balancer is not supported for high availability in an active-active (load balanced) scenario; it is only supported in an active-passive (failover) scenario. For more information, contact Oracle Support.

3.1.4 How Logon Manager Handles and Stores Application Credentials

Logon Manager encrypts application credentials using a unique key generated when the user completes the First-Time Use (FTU) wizard. The credentials remain encrypted at all times, including in the Agent's local cache, the directory, and while in transit over the network. Logon Manager only decrypts credentials (to memory, never to disk) when a configured application requests logon, and wipes the target memory location as soon as the logon request completes. The amount of data Logon Manager stores per enabled application and per user is trivial (measurable in bytes and small kilobytes).

Note:

Oracle highly recommends enabling SSL support so that the credentials sent by the user to the directory during authentication are encrypted. If SSL is not enabled, those credentials will be sent in clear text and can be intercepted by a packet sniffer. For more information, see SSL Support.

3.1.5 Further Reading

An in-depth discussion of the Logon Manager software architecture is beyond the scope of this guide. To obtain Oracle white papers containing additional information, contact your Oracle representative.

3.2 Designing the Logon Manager Directory Sub-Tree

Logon Manager gives you the freedom to set up the directory structure to best fit the needs of your organization. Specifically, you have the choice to store your data in a flat model, or create a hierarchy. While a flat model works fine for small deployments, growing and large deployments should utilize a hierarchy from the very beginning. The exact structure of your sub-tree will depend on the following factors:

- Number of users

- Number of applications you want Logon Manager to support

- Robustness of the existing infrastructure

- Structure of your organization.

3.2.1 Guidelines for Structuring the Logon Manager Sub-Tree

Oracle recommends that you set up your sub-tree as a hierarchy by following the guidelines below:

- Use OUs to group templates and policies by category, such as department or division, according to the structure of your organization.

- Control access at the OU level.

- Disable inheritance and grant no user rights at the Logon Manager root container, unless your environment dictates otherwise.

When set up this way, a hierarchy provides the following benefits:

- Highly visual and self-documenting tree structure. When you view your sub-tree in a directory browser, the sub-tree structure is self-descriptive and easy to follow.

- No unwanted inheritance of rights. Users will not natively inherit rights to sub-OUs that you do not want them to access. This eliminates the need to explicitly deny unwanted access rights that are being passed down the tree.

- Robust network, Agent, and directory performance. Typically, users who download large numbers of templates and policies generate more network traffic and a higher load on the directory than users who only download items relevant to their jobs. Grouping conserves your environment's resources and improves Agent response time.

- Distributed administrative tasks. Your templates are organized into easily controllable sets, and access rights determine who can manage which templates. You also have the ability to implement rights-based version control of your templates.

- Low administrative overhead. Controlling access at the template level requires setting permissions for each individual template via the Logon Manager Administrative Console; controlling access at the OU level is achieved via delegated administration using Microsoft and third-party management tools.

The figure below depicts a sample Logon Manager sub-tree whose design reflects the above best practices.

In our sample scenario, users from the Portland division do not need access to applications used by the Sacramento division, and vice versa; therefore, each division's templates and policies live in dedicated sub-OUs under the root and one division cannot access another division's sub-OU. In the end, your environment will dictate the specifics of your implementation.

Note:

Oracle highly recommends that you store templates and policies in individual OUs. To do this, you must Use Configuration Objects.

If you are starting out with a flat model, but expect the number of users and provisioned applications to grow, create a sub-container under the root and use it to store your templates and policies as a flat file until you are ready to transition to a hierarchy. Monitor the performance of your environment as you add more users and provision more applications, and transition to a hierarchy sooner rather than later to minimize the required effort. When transitioning to a hierarchy, use the existing container as your new Logon Manager root container and create sub-OUs underneath it.

3.2.2 Special Directory Objects Required by Logon Manager

To successfully synchronize with an LDAP directory, Logon Manager requires that the following directory objects are configured before attempting synchronization:

- People OU. When deploying Logon Manager with a directory other than Active Directory, application credentials cannot be stored under user objects. Instead, credentials are stored in flat format inside a special OU called People. You must create this OU as described in Creating the People OU.

- Note:

This OU is not in any way related to the People container used by Sun Directory Server to store LDAP user accounts.
Do not place the People OU inside the Logon Manager configuration object container (SSOConfig). Doing so will cause Logon Manager to parse the credentials of every Logon Manager user when loading templates, placing a significant, unnecessary load on the directory.

- vGOLocator object. This object links an LDAP user account to the user's application credentials stored in the People OU. When the user logs in, Logon Manager traverses the tree up from the user's object until the vGOLocator object is found. The vGOLocator object provides Logon Manager with the path to the People OU.

Note:

Oracle recommends placing this object inside your directory user accounts container, as shown in the diagram on page 13. If necessary, it can also be placed in the root of the directory tree, although this option is not recommended. At the very least, vGOLocator must be placed at the same level as the container that holds your user accounts.

3.2.3 Version Control and Pre-Flight Testing of Templates and Policies

Oracle recommends that you create dedicated sub-OUs for each stage of your workflow: development, staging, and production, as shown in Figure 2. This way you will be able to:

- Track changes made to templates and policies as they pass through the workflow and enter production by keeping shadow copies each time templates and policies move from one workflow stage to the next.

- Roll back to a previous version of a template or policy if need arises.

- Control who can work on which templates and policies at each workflow stage. In particular, you should strictly enforce rules governing who can put a template or a policy into production.

Always test every application template and administrative override in a contained environment before you deploy it to end-users. Testing helps you stage your changes and resolve any potential issues that would be much more costly to resolve were they to occur in production. Testing is particularly critical in large deployments: if you push out a misconfigured template or an incorrect administrative override network-wide, access to mission-critical applications may be lost enterprise-wide.

When setting up a contained test environment, create a dedicated test container to which only members of your development group will have access. Then, point the test Logon Manager Agent(s) at this container and place your templates and administrative overrides in it. Once you confirm that the templates and policies are functioning as intended, move them to the target production container.

If you decide not to keep shadow copies of your templates after you test them, move them from the test container to target production containers as follows:

1. Pull down the template from the directory.

2. Create a local backup of the template.

3. Push the duplicate into the new location within the directory.

4. Delete the template from its original location.

3.2.4 Precautions for Configuring Object Access Control Lists Using the Console

When you modify an object's Access Control List (ACL) using the Console, the connection string (repository host name or IP) used to connect to the repository is treated by the Console as a unique repository identifier and recorded in the object. The Console is thus unable to distinguish between two unique repositories and two methods to connect to the same repository.

Because of this, if you use different connection strings for the same repository, e.g. an IP address and host name, the changes made to an object from one session to the next will be lost. To work around this issue in an LDAP environment, always use the same connection string (IP address or host name) when modifying object ACLs through the Console.

3.2.5 Precautions for Upgrading the Agent and Console

To maintain template and settings compatibility throughout your environment, you should always use a version of the Console matching the oldest version of the Agent still deployed in production. Due to template schema changes between releases, older Agents may exhibit unexpected behavior when supplied a template created or modified by a newer version of the Console. For this reason, if you are upgrading to a newer release of Logon Manager, Oracle highly recommends that you do not upgrade your Console until all deployed Agent installations have been upgraded.

Note:

Even if you do not make any changes to a template, it is still rewritten using the currently installed Console's data schema when you push the template back to the repository.

3.3 Global Agent Settings vs. Administrative Overrides

The behavior of the Logon Manager Agent, including its interaction with the directory, is governed by settings configured and deployed to the end-user machine by the Logon Manager administrator using the Logon Manager Administrative Console. The settings fall into one of the following categories:

- Global Agent settings are the "local policy" for the Agent; they are stored in the Windows registry on the end-user machine and are included in the Logon Manager MSI package to provide the Agent with an initial configuration during deployment. Global Agent settings are stored in HKEY_LOCAL_MACHINE\Software\Passlogix (32-bit systems) or HKEY_LOCAL_MACHINE\Wow6432Node\Software\Passlogix (64-bit systems).

Caution:

Users able to modify the HKLM hive can alter their global Agent settings and thus change the behavior of the Agent from the one originally intended. To ensure that a setting will not be changed by the end-user, deploy it through an administrative override.

- Administrative overrides take precedence over the global Agent settings stored in the Windows registry and constitute the "domain" policy for the Agent. Overrides are downloaded from the central repository by the Agent during synchronization and stored in the Agent's encrypted and tamperproof local cache, which makes them immune to end-user alterations. When role/group security is enabled, administrative overrides can be applied on a per-user or per-group basis; they can also be applied enterprise-wide to enforce configuration consistency for all users.

Note:

Be conservative when planning your administrative overrides. Fewer overrides mean less data to store and transfer, and thus more efficient synchronization with the central repository. Reducing the number of overrides also simplifies troubleshooting by eliminating unknowns, as administrative overrides cannot be viewed on the end-user machine.

Global Agent settings together with administrative overrides constitute the complete configuration policy for the Agent. The rest of this guide describes the recommended optimal configuration and complements the information found in the Enterprise Single Sign-On Suite Administrator's Guide.

WARNING:

Settings such as domain names and user object paths should always be thoroughly tested before deployment and not deployed as administrative overrides unless absolutely necessary. A simple mistake, such as a mistyped domain name, can render end-user workstations unable to synchronize with the directory, in which case you will not be able to propagate a correction through the Console - changes will have to be made to user machines using other tools.

The figure below depicts a typical view of the Logon Manager Administrative Console set up for synchronization with an LDAP directory.

The next section describes best practices for configuring Logon Manager for synchronization with LDAP. If you need additional information on settings described in this guide, see the online help included with the Console.

Note:

Before you begin, make sure that the Logon Manager Agent and the LDAP synchronizer plug-in are installed on your machine; otherwise, AD settings will not be displayed in the Console. For installation instructions, see the installation guide for your version of Logon Manager.

Tip:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

The best practice for settings not described in this guide is to leave them at their default values, unless your environment dictates otherwise. The default value is automatically in effect whenever the check box for the setting in the Logon Manager Administrative Console is not checked. The value is visible in the inactive field next to the check box.

3.4 Recommended Global Agent Settings

This section lists Oracle-recommended best-practice global Agent settings. Configure the settings as described below and include them in the customized Logon Manager MSI package. (For instructions on creating the package, see the section "Packaging Logon Manager for Mass Deployment" in the Enterprise Single Sign-On Suite Installation Guide.)

3.4.1 Select the Correct Repository Type

Before you begin configuring Logon Manager's synchronization settings, you must inform Logon Manager which supported directory you are using. This allows Logon Manager to correctly interpret the repository structure and store its data without interfering with the repository's built-in data structures.

Note:

If your repository is not listed above, select Unspecified LDAP Directory (default) from the drop-down list for backwards compatibility in upgrade scenarios; otherwise select Generic LDAP Directory. For a list of supported directories, see the Oracle Fusion Middleware Certification Matrix.

Located in: Global Agent Settings > Live > Synchronization > LDAPExt

To set: Select the check box, then select your repository from the drop-down list.

3.4.2 Configure a Server List with Desired Failover Order

In LDAP environments, server URLs must be explicitly provided to Logon Manager. Oracle highly recommends using at least two physical directory servers and placing them behind a load balancer for automatic, transparent failover. If you choose not to use a load balancer, arrange the server URLs in order of geographic proximity to the end-user so that the performance hit due to physical distance between the end-user and the next available server is minimized. For more information on load balancing, see Benefits of Load-Balancing a Logon Manager Deployment.

Located in: Global Agent Settings > Live > Synchronization > LDAPExt

To set: Select the check box, click the (…) button, and enter the desired values (one per line) as shown below. When you are finished, click OK.

3.4.3 Specify the Path to the Logon Manager Configuration Objects

You must specify the location of the Logon Manager root container (which stores Logon Manager configuration objects) for Logon Manager to store data in Active Directory.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT

To set: Select the check box, click the (…) button, and enter the desired value. When you are finished, click OK.

3.4.4 Use Configuration Objects

When deploying with an LDAP directory, Oracle highly recommends that you use directory objects for storing user and configuration data, allowing hierarchical storage, as well as role/group-based access control for individual containers, templates, and policies as described in Designing the Logon Manager Directory Sub-Tree. If you disable this feature, Logon Manager will store all template and configuration data as a single flat file in the Logon Manager root container.

Located in: Global Agent Settings > Live > Synchronization

To enable: Select the check box, then select Yes from the drop-down list.

3.4.5 SSL Support

Logon Manager repository synchronizers ship with SSL support enabled and Oracle highly recommends that you do not disable it. Your environment should always utilize SSL for all connections to the Logon Manager and other repositories for maximum security.

Note:

You must configure your environment for SSL connectivity before enabling this option.

Located in: Global Agent Settings > Live > Synchronization >LDAPEXT

To re-enable (if disabled): Deselect the check box.

3.4.6 Specify the Path(s) to User Accounts

You must specify the location of the container(s) holding user accounts in your directory. If your directory stores user accounts in multiple locations, you can specify multiple paths. Follow the guidelines below when configuring this option:

- When the Enable Directory Search for Users option is enabled, do not specify the directory root as a value here. Doing so will cause Logon Manager to parse the entire directory if a user enters an invalid user name.

- When specifying paths, be as specific as possible to avoid extra account searches if the path you specify happens to be too broad. On the other hand, if the number of locations is excessive, it can help to specify a common parent container here to reduce the complexity of your configuration.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT

To let Logon Manager search for user accounts: deselect the check box (default setting).

To set: Select the check box, click the (…) button, and enter the desired values (one per line), as shown below. When you are finished, click OK.

3.4.7 Enable Directory Search for Users

If you do not want to specify exact paths to user accounts in your directory (for example, if they are spread out over a large number of locations), enable this option to allow Logon Manager to search for user accounts within one or more locations set in Specify the Path to the Logon Manager Configuration Objects. This feature requires anonymous bind access to the directory; if you do not wish to grant anonymous bind access to your directory, but still want to enable the directory search feature, you must specify a user with directory search rights using the Bind User DN and Bind User Password fields.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT > Special Purpose

To set: Select the check box, then select Yes from the drop-down menu.

3.4.8 Set the Naming Attribute String

If you are using Novel eDirectory, you must set the value of the Naming attribute string option to cn. For other LDAP directories, consult your directory team to find out how to configure this option.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT > Special Purpose

To set: Select the check box, then enter the desired value.

3.4.9 Decide Whether to Prompt the User when Disconnected from the Directory

Use the Prompt when disconnected option to decide whether Logon Manager should prompt the user to re-authenticate to the directory upon authentication failure or disconnection. Oracle recommends that you leave this setting at its default value of No; doing so will avoid unnecessary confusion and helpdesk calls.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT

To set: Select the check box, then select the appropriate option from the drop-down list.

This option is directly related to the Credentials to use option described above and has no effect if Allow disconnected operation is set to No.

3.4.10 Share LDAP Synchronizer Credentials with Authenticators

In certain scenarios, you can reduce the number of authentication prompts end users receive by sharing the LDAP synchronization credentials with one or more authenticators. See Selecting and Configuring an Authenticator for more information.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT

To set: Select the check box, then enter the names of target authenticators, separated by commas.

Use the following authenticator identification strings, depending on the authenticator(s) in use:

Authenticator

Identification String

Windows v1 (deprecated)

WinAuth

Windows v2

MSAuth

LDAP v1

LDAP

LDAP v2

LDAPAuth

3.4.11 Add the LDAP Synchronizer to the Synchronizer Order List

Ensure that the LDAP (LDAPEXT) synchronizer plug-in is present and enabled in the Synchronizer Order list if at least one of the following is true for your environment:

- Logon Manager is synchronizing with more than one repository.

- Logon Manager is using roaming synchronization.

- Kiosk Manager is installed in your environment.

Note:

Instructions for configuring Logon Manager for multi-repository and roaming synchronization, as well as installing and configuring Kiosk Manager, are beyond the scope of this guide. For more information, see the documentation for your version of Logon Manager and/or Kiosk Manager.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then click the (…) button. In the list that appears, select the checkbox next to LDAPEXT and click OK. Use the up/down arrows to set synchronization order as necessary.

3.4.12 Set the Authentication Prompt Window Title

Oracle recommends that you use this option to give the directory authentication prompt a descriptive title so that end users know what credentials to enter when the prompt appears.

Located in: Global Agent Settings > Live > Synchronization > LDAPEXT

To set: Select the check box, then enter the desired text.

3.4.13 Make the Logon Manager Agent Wait for Synchronization on Startup

To ensure that users always have the most recent credentials, application templates, password policies, and administrative overrides, configure the Agent to wait for synchronization on startup. When this option is enabled, the Agent checks whether the directory is online. If the directory is online, the Agent does not respond to application logon requests until it successfully synchronizes with the directory. If the directory is offline, the Agent does not attempt to synchronize and starts immediately.

Located in: Global Agent Settings > Live > Synchronization

To set: Select the check box, then select Yes from the drop-down list.

3.4.14 Use Optimized Synchronization

Optimized synchronization instructs the Logon Manager Agent to synchronize only credentials that have changed since the last synchronization. Do one of the following, depending on your environment:

- Enable this option to improve synchronization performance on deployments with large numbers of credentials per user.

- Disable this option to improve synchronization performance on deployments with fewer than five credentials per user and large number of templates downloaded per user.

Located in: Global Agent Settings > Live > Synchronization

Use the default value (Yes) unless your environment requires otherwise.

3.4.15 Restrict Disconnected Operation

During deployment, configure the Logon Manager Agent not to run if a connection to the directory cannot be established. This will prevent users from completing the First-Time Use (FTU) wizard when the Agent is not connected to the directory and no local cache is present. By not allowing the Agent to run when the directory is not available, you avoid a common situation in which a second set of encryption keys is created when a user completes the FTU wizard while disconnected from the directory.

Note:

See section "Configuring Logon Manager" in the Enterprise Single Sign-On Suite Administrator's Guide for more information on this required best practice.

Located in: Global Agent Settings > Synchronization

To set: Select the check box, then select No from the drop-down list.

3.5 Recommended Administrative Overrides

Directory synchronization settings, such as domain names and object paths, should not be deployed as administrative overrides. (See Global Agent Settings vs. Administrative Overrides for an explanation.) The recommended best-practice overrides are described in the "Configuring Logon Manager" in the Enterprise Single Sign-On Suite Administrator's Guide.

3.6 Overview of the Deployment Process

This section provides a brief high-level overview of the Logon Manager deployment process an LDAP directory. Make sure you have read all of the preceding sections of this document before proceeding with deployment. Deploying Logon Manager with an LDAP directory requires you to:

1. Obtain the following documents:

- The latest version of this document

- Oracle Enterprise Single Sign-On Suite Installation Guide

- Oracle Enterprise Single Sign-On Suite Administrator's Guide

2. Install the Logon Manager Agent and the Logon Manager Administrative Console on a machine within your domain, as described in the installation guide for your version of Logon Manager. Make sure you select the LDAP Synchronizer plug-in when installing the Agent.

3. Complete the steps in Preparing the Directory for Logon Manager:

1. Extend the directory schema with Logon Manager classes and attributes.

2. Create the People OU, which will store each user's application credentials.

3. Create the vGOLocator object.

4. Create the configuration object container and the desired tree structure.

4. Configure Logon Manager as follows:

1. Complete the steps in Selecting and Configuring an Authenticator.

2. Complete the steps in Configuring the LDAP Synchronizer.

3. Configure the options described in Recommended Global Agent Settings in this guide.

4. Configure the options described in the "Configuring the Logon Manager Agent" section of the Enterprise Single Sign-On Suite Administrator's Guide.

Note:

For detailed descriptions of the settings in question, see the Console's online help. The online help is available via the Console's Help menu.

5. On a test machine, do the following:

- Create a pilot set of core templates and policies.

- Finalize the end-user experience by testing each core template, global Agent setting, and administrative override that will be deployed into production.

6. Create a custom MSI package and deploy it to end-user machines by completing the steps in the "Packaging Enterprise Single Sign-On Suite for Mass Deployment" section of the Enterprise Single Sign-On Suite Installation Guide.

7. Create, test, and deploy the remaining application templates. See the guide Configuring and Diagnosing Logon Manager Application Templates for in-depth information on provisioning different types of applications.

3.7 Preparing the Directory for Logon Manager

This section describes the basic procedures for preparing the directory for use with Logon Manager. The preparation consists of extending your directory schema with Logon Manager classes and attributes, allowing Logon Manager to store credentials under respective user objects, and creating the desired tree structure. Before starting this procedure, make sure that you have installed the Administrative Console.

3.7.1 Extending the Schema

1. Start the Suite Administrative Console.

Note:

In a development or staging environment, disable the option Check for publisher's certificate revocation in Internet Explorer to eliminate a delay when the Console starts and your machine is not connected to the Internet. (The delay is caused by Internet Explorer attempting to look up the server's certificate and timing out when a certificate authority cannot be reached.) Do not disable this option on production machines.

2. In the Console, select Extend Schema from the Repository menu. The Console displays the "Connect to Repository" dialog.

4. In the Server Name field, enter a fully qualified IP address, hostname, or NetBIOS name of your schema master domain controller.

5. In the Repository Type drop-down list, select the desired LDAP directory type.

6. Enter the port number on which your directory is listening for connections. The default ports are 636 for SSL connections and 389 for non-SSL connections.

7. (Optional) If the directory server has been configured to use SSL, leave the Use secure channel (SSL) option selected; otherwise, deselect it. (See SSL Support for more information.)

8. In the Username/ID and Password fields, enter the credentials of the account you want Logon Manager to use to connect to the directory. Depending on your environment, you may need to include the corresponding domain name as part of the user name, for example: DOMAIN\user.

9. Click OK and wait for the Console to perform the schema extension. The Console displays a status dialog showing the progress. When the schema has been successfully extended, a confirmation message appears in the status dialog:

11. Click Close.

3.7.2 Creating the Sub-Tree Root and the Configuration Object Container

Note:

While it is possible to use an existing container for storing Logon Manager data, doing so may impair directory performance. Oracle highly recommends that you create a dedicated container as the sub-tree root.

1. In the Logon Manager Administrative Console, select the Repository node in the tree.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Repository" dialog.

3. Fill in the fields as explained in steps 3-7 on page 29 and click OK to connect.

4. Create the container that will serve as the Logon Manager sub-tree root:

1. In the tree, right-click the desired parent container and select New Container from the context menu, as shown below:

The Console displays the "New Container" dialog:

2. In the "New Container" dialog, enter the desired name and click OK.

Note:

Unless your environment calls for a specific name this container, Oracle recommends that you use the default name, ESSO.

5. Create the Logon Manager configuration object container (SSOConfig):

1. In the tree, right-click Logon Manager sub-tree root and select New Container from the context menu, as shown below:

2. The Console displays the "New Container" dialog:

3. In the "New Container" dialog, enter the desired name and click OK.

Note:

Unless your environment calls for a specific name for this container, Oracle recommends that you use the default name, SSOConfig.

6. Repeat step 5 to create any additional containers you may need.

3.7.3 Creating the People OU

You must create the People OU that will hold application credentials for Logon Manager users. Oracle recommends placing the People OU inside the Logon Manager sub-tree root.

Note:

Do not place the People OU inside the Logon Manager configuration object container (SSOConfig). Doing so will cause Logon Manager to parse the credentials of every Logon Manager user when loading templates, placing a significant, unnecessary load on the directory.

Sun Directory Server stores user accounts in a container named People in the root of the directory. You must not use that container to store Logon Manager application credentials; instead, create the Logon Manager People OU in another parent container.

To create the People OU:

1. In the Logon Manager Administrative Console, select the Repository node in the tree.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Directory" dialog. Fill in the fields as explained in steps 3-7 on page 29 and click OK to connect.

3. In the tree, right-click the root of the Logon Manager sub-tree, and select Create People Container.

4. Verify that the People OU now exists at the target location.

If the People OU does not appear after you complete the above steps, or if you receive errors indicating naming violations or other problems in the directory, consult the vendor documentation for your directory for possible causes and remedies.

3.7.4 Creating the vGOLocator Pointer Object

Once you have created the People OU, you must create the vGOLocator pointer object that will link user accounts to user application credentials stored in the People OU.

Note:

You must create the vGOLocator object at least at the same level as the container that holds user accounts. Ideally, vGOLocator should exist inside the directory's user accounts container.

To create the vGOLocator object:

1. In the Logon Manager Administrative Console, select the Repository node in the tree.

2. Click the Click here to connect link in the right-hand pane. The Console displays the "Connect to Repository" dialog. Fill in the fields as explained in steps 3-7 on page 31 and click OK to connect.

3. In the tree, right-click your directory's user account container (dc=oracle,ou=People in our Sun Directory Server-based example) and select Add Locator Object from the context menu, as shown below:

4. In the "Add Locator Object" dialog that appears, do the following:

1. In the Name field, enter default.

2. In the Forwarding Location field, enter the full path to the container that holds the People OU. (Alternatively, you may navigate to and select the target container using the tree.)

3. Click OK.

4. Verify that the vGOLocator object appears at the destination location.

3.8 Selecting and Configuring an Authenticator

An authenticator is necessary to uniquely authenticate the user to Logon Manager. In an LDAP environment, you have the choice to select one of the following authenticators, based on your configuration:

- Windows Password Authenticator (Version 2). Oracle highly recommends using this authenticator, as it allows to eliminate authentication prompts when the following conditions are met (see Share LDAP Synchronizer Credentials with Authenticators for more information):

- The user has an Active Directory or NT domain account.

- The LDAP directory credentials are synchronized with Active Directory or the NT domain.

- LDAP Authenticator (Version 2). Use this authenticator if you cannot uniquely identify the user based on the machine logon, for example in kiosk or other environments where users are logged in generically, or when the user has no Active Directory or NT domain account. Users will receive additional authentication prompts in this scenario unless their synchronization and user credentials are identical (see Share LDAP Synchronizer Credentials with Authenticators for more information).

3.9 Configuring the LDAP Synchronizer

After you have prepared LDAP for Logon Manager, you must configure the LDAP synchronizer for your environment. Configure these settings on your "template" client machine and include them in the MSI package you will use to deploy Logon Manager to end-users. Before starting this procedure, make sure that the Logon Manager Administrative Console and the Logon Manager Agent (including the LDAP synchronizer plug-in) are installed.

Note:

Do not include application templates in the MSI package as they will not function in a directory-synchronized environment. The ability to include templates directly in the MSI package is for specialized use only. Instead, push them to the directory for automatic retrieval by the Logon Manager Agent.

1. Launch the Logon Manager Administrative Console.

2. In the left-hand pane, right click the Global Agent Settings node, then selectImport > From Live HKLM from the context menu. The Console imports the current Agent settings from the Windows registry.

3. Configure the Agent as described in Recommended Global Agent Settings and Recommended Administrative Overrides.

Note:

When the check box next to a setting is unchecked, the default value for the setting (shown grayed-out to the right of the check box) is in effect.

4. Save your configuration to an XML file for future reference. From the File menu, select Save, enter the desired file name, and click Save. If you change your settings, you can load this XML file into the Console to revert back to your original choices.

5. From the Tools menu, select Write Global Agent Settings to HKLM. The Console writes your changes to the registry and restarts the Agent.

4 Appendix A: Minimum Administrative Rights for Logon Manager Repository Objects

This appendix lists the minimum administrative rights that must be granted to specific Logon Manager objects for Logon Manager to function.

Note:

Information in this appendix is provided for your reference. By default, Logon Manager automatically sets the appropriate rights when you extend your repository schema. If necessary, these rights can be manually granted and modified directly the repository.

4.1 Minimum Administrative Rights Required by Logon Manager Containers

You must grant the following administrative rights to each container in which you want Logon Manager to store templates, policies, and other configuration items:

- List Contents

- Read All Properties

- Write All Properties

- Delete

- Read Permissions

- Modify Permissions

- Modify Owner

- Create vGOConfig Objects

- Delete vGOConfig Objects

- Create Organizational Unit Objects

- ·elete Organizational Unit Objects

4.2 Minimum Administrative Rights Required for Credential Auditing

You must grant the following administrative rights to vGOUserData and vGOSecret objects to audit user credentials:

For vGOUserData objects:

- List Contents

- Read All Properties

For vGOSecret objects:

- List Contents

- Read All Properties

4.3 Minimum Administrative Rights Required for Credential Deletion

You must grant the following administrative rights to vGOUserData and vGOSecret objects in order to delete user credentials:

Note:

Users able to delete credentials are automatically able to audit them.

For vGOUserData objects:

- List Contents

- Read All Properties

- Delete

- Delete Subtree

- Delete All Child Objects

For vGOSecret objects:

- List Contents

- Read All Properties

- Delete

- Delete Subtree

- Delete All Child Objects

5 Appendix B: Logon Manager Repository Object Classes and Attributes

This appendix describes the directory classes, attributes, and access rights that Logon Manager adds to your directory during schema extension.

5.1 vGOUserData

vGOUserData objects are containers that store application credentials. (Credentials are stored as objects of type vGOSecret.)

Attributes:

Attribute Name

Syntax

Flag

vGOSecretData

Case Ignore String

Singled Valued, Synchronize

vGORoleDN

Not Used

Other optional attributes

ou, dn, cn, o

Access rights: Users can read and write the above attributes under their own user objects. The administrator has full rights but will not be able to read the encrypted children (vGOSecret) of this object.

5.2 vGOSecret

vGOSecret objects store all user secrets, including an object that stores each user's application credentials and deleted objects. This is added to the vGOUserData object as an auxiliary class.Attributes:

Attribute Name

Syntax

Flag

vGOSecretData

Case Ignore String

Singled Valued, Synchronize

vGOSharedSecretDN

Not Used

Other optional attributes

ou, dn, cn, o

Access rights: As inherited from the vGOUserData object, plus: all users can read this object; only the owner can write to this object; and only the owner or an administrator can delete this object.

5.3 vGOConfig

vGOConfig objects are containers that store Logon Manager configuration objects such as application templates, password generation policies, and administrative overrides.

Attributes:

Attribute Name

Syntax

Flag

vGOConfigType

Case Ignore String

Singled Valued, Synchronize

vGOConfigData

Case Ignore String

Singled Valued, Synchronize

vGORoleDN

Not Used

Other optional attributes

ou, dn, cn, o

Access rights: All users have read-only rights to the attributes within this object. The administrator has full rights.

5.4 vGOLocatorClass

vGOLocatorClass is a pointer object class. Objects of this class point the Logon Manager Agent to the location in which user credentials should be stored.

Attributes:

Attribute Name

Syntax

Flag

vGOLocatorAttribute

Case Ignore String

Single Valued

Other optional attributes

dn, cn, o

Access rights: All users have read, compare, and search rights to these attributes for all objects of this class; the administrator has all rights.

6 Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory

This appendix contains descriptions of issues that may arise during deployment of Logon Manager, and instructions for remedying those issues.

6.1 Active Directory Schema Extension Failures

If the AD schema extension fails, follow the steps below to identify and remedy the possible cause:

1. Check the following, then retry extending the schema:

- The machine from which you are performing the extension is on the same domain as the directory.

- You are performing the extension against the schema master DC.

- You are logged on as the schema administrator.

2. If schema extension still fails, install the Logon Manager Administrative Console directly on your schema master DC and perform the schema extension locally. This solution rules out all possible network issues (such as DNS problems) and does not fail unless your AD schema contains errors.

3. If you are still unable to extend your schema, the schema might be damaged. Check the health of your schema using Microsoft's MOM tool and make sure your schema adheres to Microsoft's best practices described in the following MS TechNet article: http://technet.microsoft.com/en-us/library/bb727085.aspx

6.2 All Users Unable to Store Credentials Under User Objects

When you enable the storage of credentials under user objects, Logon Manager grants all users rights to create objects of type vGOUserData and vGOSecret. These rights are granted at the directory root and are inherited all the way through to the respective user objects. When these rights are not granted or inherited properly, users are unable to store application credentials under their respective user objects. Possible points of failure include:

- The necessary rights have not been granted. You must instruct Logon Manager to set the necessary rights by selecting Enable storage of credentials under the user object (AD only) from the Repository menu in the Logon Manager Administrative Console.

- The rights were granted at the parent domain instead of the user-specific child domain and have not propagated to the child domain. In such case, you can use the Console running on the parent domain DC to grant the necessary rights automatically, or manually grant the rights at the root of each child domain and wait for them to propagate to the user objects.

Note:

If the issue affects only certain groups of users, specifically members of Administrators, Power Users, and other protected groups, see Appendix C: Troubleshooting Logon Manager on Microsoft Active Directory.

6.3 Select Users Unable to Store Credentials Under User Objects

The rights necessary to store credentials under user objects are granted at the tree root and inherited down to user objects. When only select users (specifically, members of protected user groups such as Administrators), are unable to store credentials under user objects, the most likely cause is blocked rights inheritance caused by the AdminSDHolder object. The object's ACL, which governs the ACLs of all protected groups, prohibits rights inheritance by default. More information about this issue is available in the following MS Knowledge Base article: http://support.microsoft.com/kb/817433.

The following protected user groups are known to be affected by this problem:

- Enterprise Admins

- Schema Admins

- Domain Admins

- Administrators

- Account Operators

- Server Operators

- Print Operators

- Backup Operators

- Cert Publishers

To verify that you are experiencing this particular issue, do the following:

1. Log in to the primary DC as a domain administrator.

2. Open the Microsoft Management Console and load theActive Directory Users and Computers snap-in.

3. From the View menu, select Advanced Features.

4. Navigate to the affected user object, right-click it, and select Properties.

5. In the dialog that appears, select the Security tab.

6. Click Advanced. The "Advanced Security Settings" dialog appears:

7. In the dialog, check whether:

1. The Allow inheritable permissions… check box is not selected.

2. The permissions highlighted in the figure in step 6 are not present in the list.

If the above conditions are true, the user object is not inheriting the necessary permissions from the directory root.

To rectify this issue, you must manually modify the ACL of the AdminSDHolder object to grant the right to create objects of type vGOConfig and vGOUserData. The steps are as follows:

1. Log in to the primary DC as a domain administrator.

2. In the Microsoft Management Console, open the Active Directory Schema snap-in.

3. In the left-hand tree, drill down the Classes node and locate the vGOUserData node.

4. Right-click the vGOUserData class and select Properties from the context menu.

5. In the dialog that appears, select the Relationship tab.

6. Click the Add Superior button.

7. In the dialog that appears, select container from the drop-down list and click OK. The "container" class appears in the Possible Superior field.

8. Click OK to close the properties dialog.

9. In the Microsoft Management Console, open the Active Directory Users and Computerssnap-in.

10. From the View menu, select Advanced Features.

11. Navigate to the AdminSDHolder container located in: cn=AdminSDHolder,cn=System,dc=<domainName>,dc=<domainSuffix>

12. Right-click the AdminSDHolder container and select Properties.

13. In the "Properties" dialog, select the Security tab and click Advanced.

14. In the "Advanced Security Settings" dialog, click Add… .

15. In the "Select User, Computer, or Group" dialog, enter SELF and click OK.

16. In the "Permission Entry" dialog, do the following:

1. In the Apply onto: drop-down list, select This object and all child objects.

Note:

If the create and delete permissions for vGOUserData objects do not appear in the permissions list, select User objects from the Apply onto: drop-down list instead. This variation occurs between different versions and patches of Active Directory and the underlying operating system.

2. In the list of permissions, select the Allow check box for the permissions highlighted below:

3. Click OK.

17. Trigger the SD propagator (SDPROP) process to immediately propagate the changes throughout the network. Instructions for launching the SD propagator process are provided in the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/251343.

Note:

If you encounter a version of this procedure that calls to apply the above permissions onto "This object only," disregard it. It is deprecated and has been superseded by the steps above.

7 Troubleshooting Logon Manager
on Microsoft AD LDS (ADAM)

If Logon Manager is unable to connect to the target AD LDS (ADAM) instance, try connecting to your AD LDS (ADAM) instance directly using the ADSIEdit tool. If you still cannot connect, the possible causes are described below

7.1 The Target AD LDS (ADAM) Instance is Not Running

Your AD LDS (ADAM) instance runs as a service on the target server. Use the Computer Management MMC snap-in on the target server to check whether the AD LDS (ADAM) instance is running by doing the following:

1. Open the Computer Management console. (The quickest way is to right-click on My Computer and select Manage from the context menu.)

2. In the left-hand pane select Services. The console displays a list of services installed on the system.

3. Locate your AD LDS (ADAM) instance in the list.

4. If the instance's status is "Stopped," start it as follows:

1. Double-click the instance. The instance's property dialog box appears.

2. Ensure that the Startup Type option is set to Automatic (if it isn't, set it).

3. Click Start and wait for the instance to initialize.

4. Click OK to close the property dialog box.

If the instance's status is "Started" and you still cannot connect, you may be connecting to the instance using the wrong port. See the next section for more information.

7.2 AD LDS (ADAM) Instance is Running on Non-Default Ports

If you configured your AD LDS (ADAM) instance to use custom ports, you must instruct Logon Manager (and other software, such as ADSIEdit) to use those ports when connecting to the AD LDS (ADAM) instance. To troubleshoot this issue, do the following:

- To check the ports on which the target AD LDS (ADAM) instance is running, see AD LDS (ADAM) documentation.

- To check (and correct) the ports Logon Manager uses to connect to AD LDS (ADAM), examine the contents of the Servers field in the Console. Logon Manager uses the default port (636 for SSL connections, 389 for non-SSL connections) unless a specific port number is appended to the server URL, for example dc1.company.com:9448.

7.3 Account Used to Connect to AD LDS (ADAM) Does Not Have the Required Privileges

If Logon Manager cannot connect to AD LDS (ADAM), check whether the user account used to connect to AD LDS (ADAM) has the required privileges. To check and set the privileges for a user account, see the operating system and AD LDS (ADAM) documentation.

8 Appendix E: Creating the Required User Groups on AD LDS (ADAM)

This appendix describes how to create the required user groups in Active Directory for use with Logon Manager deployed on an AD LDS (ADAM) instance.

The groups are:

- SSOAdmins. This group contains at least two users who hold administrative privileges over the target AD LDS (ADAM) instance. This group should also contain users who need to create and push application templates.

Caution:

When creating the instance, specify this group as the administrative user group. If you specify a single user, you risk locking yourself out of your Logon Manager deployment if the single account becomes inaccessible.

- SSOUsers. This group contains all other Logon Manager users.

To create the SSOAdmins and SSOUsers groups and place the desired users in these groups:

Note:

This procedure assumes you have decided which users will belong in which groups and that the target user accounts already exist.

1. Log on to your domain controller as the administrator.

2. Open the Active Directory Users and Computers console snap-in.

3. In the console, expand the target domain and right-click the Users node.

4. In the context menu, select New> Group.

5. In the "New Object - Group" dialog, do the following:

1. Enter the group name shown above.

2. Select the Global group scope.

3. Select the Security group type.

4. Click OK.

5. The new group appears in the list of objects in the right-hand pane of the console.

6. In the list of objects, double-click the group you just created. The group properties dialog box appears.

7. In the group properties dialog, do the following:

1. Select the Members tab.

2. Click Add.

3. In the dialog box that appears, enter the target user name and click Check Names to verify the user name. If you receive an error, correct any spelling mistakes and click Check Names again; when the user name is validated, click OK.

4. Repeat steps 7b and 7c for each additional user you want to include in the group.

5. When you have added the desired users to the group, click OK to close the group properties dialog box.

8. Repeat steps 4-7 to create and configure the SSOUsers group.

9 Appendix F: Configuring Oracle Internet Directory

To use Logon Manager with Oracle Internet Directory, you must enable anonymous binding and disable the access control check feature in Oracle Internet Directory as follows:

1. Launch a browser and open Oracle Directory Services Manager.

2. Log on as the super user, orcladmin.

3. Click Connect to a directory and select the target instance.

4. Click the Data Browser tab.

5. Navigate to the following location:cn=oid1,cn=osdldapd,cn=subconfigsubentry Change the value of the orclanonymousbindsflag from 2 to 1, then click Apply.

6. Disable the "Enable Access Control Check" feature:

1. In the Oracle Enterprise Manager Fusion Middleware Control application, locate the target Oracle Internet Directory instance.

2. From the Oracle Internet Directory menu, select Administration> Server Properties.

3. On the Server Properties screen, disable the Enable Access Control Check option.

4. Click Apply.

10 Appendix G: Configuring Oracle Virtual Directory

To use Logon Manager with Oracle Virtual Directory, you must enable anonymous binding and disable the access control check feature in Oracle Virtual Directory as follows:

- Map the user containers of all LDAP servers to the same subtree of the Oracle Virtual Directory directory information tree. For example, the following is the correct layout for DSEE and OID servers mapped to the same OVD instance:

- ou=dsee,ou=users,dc=corp,dc=com (for Oracle DSEE user entries)

- ou=oid,ou=users,dc=corp,dc=com (for OID users entries)

This ensures that the Logon Manager locator-based user lookup mechanism is able to locate users on different servers.

- Ensure anonymous binding is enabled on the mapped LDAP server. Grant search permissions for user list entries to the anonymous user.

- When configuring the LDAP synchronizer via the ESSO Suite Administrative Console, the repository type you select must match the type of repository for which the OVD instance has been configured.

- Disable the "Enable Access Control Check" feature:

1. In the Oracle Enterprise Manager Fusion Middleware Control application, locate the target Oracle Virtual Directory instance.

2. From the Oracle Virtual Directory menu, select Administration > Server Properties.

3. On the Server Properties screen, disable the Enable Access Control Check option.

4. Click Apply.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2013, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.