Oracle Enterprise Single Sign-On Logon Manager Deploying Logon Manager with Microsoft Active Directory Release 11.1.2 E27161-02 August 2012
Oracle Enterprise Single Sign-On Logon Manager: Deploying Logon Manager with Microsoft Active Directory Release 11.1.2 E27161-02 Copyright 2012, 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 software or related documentation 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software 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. 2
Table of Contents Preface... 5 Audience... 5 Access to Oracle Support... 5 Related Documents... 5 Conventions... 6 Part 1: Deployment Best Practices... 7 Overview of Oracle Logon Manager... 8 Logon Manager and Active Directory Environments... 8 How Logon Manager Extends Your Active Directory Schema... 8 How Logon Manager Synchronizes with Active Directory... 9 How Logon Manager Handles and Stores Application Credentials... 9 Further Reading... 9 Designing the Logon Manager Directory Sub-Tree... 10 Guidelines for Structuring the Sub-Tree... 10 Version Control and Pre-Flight Testing of Templates and Policies... 12 Precautions for Configuring Object Access Control Lists (ACLs) Using the Console... 13 Precautions for Upgrading the Agent and Console... 13 Global Agent Settings vs. Administrative Overrides... 14 Recommended Global Agent Settings... 16 Data Storage Settings... 16 Use Configuration Objects... 16 Specify the Path to the Logon Manager Configuration Objects... 16 Store User Credentials Under Respective User Objects... 16 Repository Connection Settings... 17 Let Logon Manager Find the Nearest Domain Controller... 17 SSL Support... 18 Select the Credentials to Use when Authenticating to the Directory... 18 Decide Whether to Prompt the User when Disconnected from the Directory... 19 Let Logon Manager Search for User Accounts... 19 Add the Active Directory Synchronizer to the Synchronizer Order List... 19 Make the Logon Manager Agent Wait for Synchronization on Startup... 20 3
Use Optimized Synchronization... 20 Restrict Disconnected Operation... 21 Recommended Administrative Overrides... 21 Part 2: Deployment Procedures... 22 Overview of the Deployment Process... 23 Preparing Active Directory for Logon Manager... 24 Step 1: Extending the Schema... 24 Step 2: Enabling the Storage of User Credentials Under User Objects... 26 Step 3: Creating the Logon Manager Configuration Object Container and Sub-Tree Structure... 28 Configuring the Active Directory Synchronizer... 30 Testing the Logon Manager Configuration... 31 Next Steps... 32 Part 3: Appendices... 33 Appendix A: Minimum Administrative Rights for Logon Manager AD Objects... 34 Minimum Administrative Rights Required by Logon Manager Containers... 34 Minimum Administrative Rights Required for Credential Auditing... 34 Minimum Administrative Rights Required for Credential Deletion... 35 Appendix B: Logon Manager AD Classes and Attributes... 36 vgouserdata... 36 vgosecret... 36 vgoconfig... 37 vgolocatorclass... 37 Appendix C: Troubleshooting Logon Manager on Active Directory... 38 Active Directory Schema Extension Failures... 38 All Users Unable to Store Credentials Under User Objects... 38 Select Users Unable to Store Credentials Under User Objects... 39 4
Preface Audience This guide describes best practices and recommended procedures for deploying Oracle Enterprise Single Sign-On Manager (Logon Manager) with Microsoft Active Directory. Readers of this guide should be experienced system administrators and have a solid understanding of Active Directory and related concepts, such as directory schema, structure, and security. Oracle highly recommends that you read this guide before planning the deployment of Logon Manager as it will familiarize you with the recommended preparation and deployment steps, as well as advise you how to avoid short- and long-term problems. By following the recommendations in this and other Logon Manager Best Practices guides, you will implement an optimal Logon Manager configuration. Note: Best practices described in this guide apply exclusively to plain Logon Manager deployments on Active Directory. They do not apply to LDAP, Citrix, Terminal Services, kiosk, and Kiosk Manager environments. Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired. Related Documents We continually strive to keep our documentation accurate and up to date. For the latest version of this and other documents, visit http://download.oracle.com/docs/cd/e23906_01/index.htm. For more information, see the other documents in the documentation set for this release: Oracle Enterprise Single Sign-On Suite Plus o Release Notes o Installation Guide o Administrator's Guide o Secure Deployment Guide o User's Guide Oracle Enterprise Single Sign-On Logon Manager o Deploying Logon Manager with Microsoft Active Directory o Deploying Logon Manager with Microsoft Active Directory Application Mode and Active Directory Lightweight Directory Services o Deploying Logon Manager with a Lightweight Directory Access Protocol Directory 5
o Template Configuration and Diagnostics for Windows Applications o Template Configuration and Diagnostics for Web Applications o Template Configuration and Diagnostics for Mainframe Applications Oracle Enterprise Single Sign-On Provisioning Gateway o Administrator's Guide o Command Line Interface Guide o Oracle Identity Manager Connector Guide o Sun Java System Identity Manager Connector Guide o IBM Tivoli Identity Manager Connector Guide Oracle Enterprise Single Sign-On Universal Authentication Manager Administrator's Guide User's Guide Conventions The following text conventions are used in this document: Term or Abbreviation boldface italic monospace Description Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. 6
Part 1: Deployment Best Practices This part describes best practices for deploying Logon Manager with Microsoft Active Directory. It contains the following sections: Overview of Logon Manager Designing the Logon Manager Directory Sub-Tree Global Agent Settings vs. Administrative Overrides Recommended Global Agent Settings Recommended Administrative Overrides 7
Overview of Oracle Logon Manager 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 Plus Technical Overview white paper available from Oracle Support. Logon Manager and Active Directory Environments 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. 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. 8
Note: Schema extension is a post-installation procedure. For instructions, see Preparing Active Directory for Logon Manager. 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 AD Objects Appendix B: Logon Manager AD Classes and Attributes 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. 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 Configure SSL Support for details. 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. 9
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 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 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. 10
Figure 1 depicts a sample Logon Manager sub-tree whose design reflects the above best practices. Figure 1 Recommended Logon Manager sub-tree design 11
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 enable the use of 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. 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 on page 12. 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. 12
Precautions for Configuring Object Access Control Lists (ACLs) 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. 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. 13
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 Logon Manager Best Practices guides. 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. Figure 2 depicts a typical view of the Logon Manager Administrative Console set up for synchronization with Active Directory. 14
Figure 2 The Logon Manager Administrative Console 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 Installation and Setup 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 Logon Manager Best Practices 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 Logon Manager Administrative Console is not checked. The value is visible in the inactive field next to the check box. 15
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 guide Best Practices: Configuring Logon Manager for Mass Deployment.) Data Storage Settings Oracle recommends configuring Logon Manager s data storage settings as described below. 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 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. 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. 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. 16
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 AD 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. Repository Connection Settings Oracle recommends configuring Logon Manager s repository connection settings as described below. 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. 17
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/enus/library/aa364671(vs.85).aspx Located in: Global Agent Settings Live Synchronization ADEXT To re-enable (if disabled): Deselect the check box. 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 Plus 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. 18
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. 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. 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. 19
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 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 check box next to ADEXT and click OK. Use the up/down arrows to set synchronization order as necessary. 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. 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. 20
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. 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 Plus Secure Deployment Guide and in the Configuring the Logon Manager Agent section of the Oracle Enterprise Single Sign-On Suite Plus Administrator s Guide. 21
Part 2: Deployment Procedures This part describes the most important procedures for deploying Logon Manager with Microsoft Active Directory. It contains the following sections: Overview of the Deployment Process Preparing Active Directory for Logon Manager Configuring the Active Directory Synchronizer Testing the Logon Manager Configuration 22
Overview of the Deployment Process This section provides a brief high-level overview of the Logon Manager deployment process on MS Active Directory. Make sure you have read all of the preceding sections of this document before proceeding with deployment. Deploying Logon Manager with MS Active Directory requires you to: 1. Obtain the following documents: The latest version of this document Oracle Enterprise Single Sign-On Suite Plus Installation Guide Oracle Enterprise Single Sign-On Suite Plus 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: a. Extend the Active Directory schema with Logon Manager classes and attributes. b. Enable storage of user credentials under user objects. c. Create the desired tree structure and grant the required permissions. 4. Configure Logon Manager as follows: a. Complete the steps in Configuring the Active Directory Synchronizer. b. Configure the options described in Recommended Global Agent Settings in this guide. c. Test your configuration as described in Testing the Logon Manager Configuration. d. Configure the options described in the guide Logon Manager Best Practices: Configuring the Logon Manager Agent. 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 guide Best Practices: Packaging Logon Manager for Mass Deployment. 7. Create, test, and deploy the remaining application templates. See the Logon Manager Best Practices guides Template Configuration and Diagnostics for the target application type (Windows, Web, or mainframe) for in-depth information on provisioning different types of applications. 23
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. Instructions are provided in the following article: http://www.microsoft.com/technet/opsmgr/2005/library/dirmgmtpack/ dirmgmtpackmom_3.mspx 2. Installed the Logon Manager Administrative Console, as described in the Logon Manager Installation and Setup guide for your version of Logon Manager. Step 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. 24
6. (Optional) If you configured your domain controllers to use SSL, leave the Use secure channel (SSL) option enabled; otherwise, disable it. (See Configure 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 for troubleshooting steps. 9. Click Close. 25
Step 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: a. 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 at: http://technet2.microsoft.com/windowsserver/en/library/ 8c76ff67-9e9d-4fc7-bfac-ffedee8a04d41033.mspx?mfr=true b. Expand the Classes node and navigate to the vgouserdata class. c. Right-click the vgouserdata class and select Properties from the context menu. d. In the vgouserdata Properties dialog, select the Relationship tab. 26
e. Check whether the user class appears in the Possible Superior field: If the user class does not appear as a possible superior, see All Users Unable to Store Credentials under User Objects in Appendix C for possible causes and remedial steps. 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 for instructions on how to remedy this issue. 27
Step 3: Creating the Logon Manager 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: 28
29
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. 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 select Import 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. 30
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 select Import 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. 31
Next Steps Read the guides Best Practices: Configuring the Logon Manager Agent and Best Practices: Packaging Logon Manager for Mass Deployment to complete the configuration of Logon Manager and deploy it to end-user machines. 32
Part 3: Appendices This part provides material supplementing the information included earlier in this guide. It contains the following appendices: Appendix A: Minimum Administrative Rights for Logon Manager AD Objects Appendix B: Logon Manager AD Classes and Attributes Appendix C: Troubleshooting Logon Manager on Active Directory 33
Appendix A: Minimum Administrative Rights for Logon Manager AD 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 Active Directory schema. If necessary, these rights can be manually granted and modified directly in Active Directory using the Microsoft Management Console. 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 Delete Organizational Unit Objects 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 34
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 35
Appendix B: Logon Manager AD Classes and Attributes This appendix describes the directory classes, attributes, and access rights that Logon Manager adds to your directory during schema extension. 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. 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. 36
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. 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. 37
Appendix C: Troubleshooting Logon Manager on Active Directory This appendix contains descriptions of issues that may arise during deployment of Logon Manager, and instructions for remedying those issues. 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 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 Select Users Unable to Store Credentials under User Objects. 38
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 the Active 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. 39
6. Click Advanced. The Advanced Security Settings dialog appears: 7. In the dialog, check whether: a. The Allow inheritable permissions check box is not selected. b. 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. 40
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 Computers snap-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: a. 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. b. In the list of permissions, select the Allow check box for the permissions highlighted below: 41
c. 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. 42