BHOLD FIM Integration Installation
Updated: January 11, 2013
Applies To: Forefront Identity Manager 2010
The BHOLD FIM Integration module adds self-service role management to Microsoft Forefront Identity Manager, making it possible for users to request additional roles and enforcing who can take on those roles. The BHOLD FIM Integration module extends the FIM Portal to make it easy to manage users’ roles as part of overall FIM administration.
This topic describes how you must configure your network infrastructure to enable you to install and use the BHOLD FIM Integration module. It also covers how to install the BHOLD FIM Integration module and configuration that is required after you install the BHOLD FIM Integration module.
The BHOLD FIM Integration module extends the FIM Portal and FIM Service to allow users to manage their roles within the FIM Portal. For this reason, it is essential that the BHOLD Core module and the necessary FIM features be installed and configured before installing the BHOLD FIM Integration module.
The following are the software components that must be present on the computer before you can install the BHOLD FIM Integration module:
Microsoft FIM 2010 R2 SP1 Portal and Service
Microsoft Silverlight 3 or later
Internet information Services and ASP.NET
Microsoft Silverlight Tools
In addition, the BHOLD Core and Access Management Connector modules must already be deployed on a server in the environment, and FIM must be configured with one or more BHOLD management agents. For information about installing and configuring the BHOLD Core module, see BHOLD Core Installation. For information about installing and using the Access Management Connector module, see Access Management Connector Installation and Test Lab Guide: BHOLD Access Management Connector.
For information about installing FIM Portal and other FIM features, see Planning and Architecture in the Microsoft Forefront Technical Library.
The name of the FIM service database must be FIMService. BHOLD FIM Integration setup will fail if FIM was not installed with the default FIM service database name.
Before you begin to install the BHOLD FIM Integration module, you must create a BHOLD directory in the root directory of the C: disk drive (C:\BHOLD).
In addition, you need to be prepared to provide the information that the BHOLD FIM Integration Setup wizard requires to complete the installation. The following worksheet will help you record that information so you will be ready to supply it when it is needed.
|Use Security Provider on Domain||When selected, specifies that Active Directory Domain Services security will control access to BHOLD Core.||Select the check box. Important: The installation will fail if this check box is not selected.|
|Domain||Specifies the domain containing the service account that you created when installing BHOLD Core. For more information, see BHOLD Core Installation.||The domain name is supplied automatically by the wizard. Change the name only if it is incorrect. Important: Specify the domain name by using the NetBIOS (short) name, not the fully qualified domain name (FQDN). For example, if the FQDN of the domain is fabrikam.com, specify the domain name as FABRIKAM.|
|Username||Specifies the logon name of the BHOLD Core service user account.||Write the user account name here:|
|Password||Specifies the password of the service user account.||Write the password here: Important: Be sure to keep this password in a hidden, secure location.|
|User||Specifies the logon name of an account with administrator privileges for FIM. Microsoft strongly recommends that you do not use the account associated with the root user in BHOLD Core (by default, the account used to install BHOLD Core).||Write the user account name here:|
|Password||Specifies the password of the FIM administrator user account.||Write the password here: Important: Be sure to keep this password in a hidden, secure location.|
|FIM Database||Specifies the name of the FIM Service database.||FIMService|
|Website IP/Port||Specifies the name or IP address of the FIM Portal server and the website port.||Write the server name or address and port here:|
|Domain||Specifies the name of the domain of the account specified in User, below. Specify the domain in NetBIOS (short) format.||Write the user account domain name here?|
|User||Specifies the logon name of the account of a BHOLD user that is a supervisor of all users and roles and has permission to link and unlink user roles. Microsoft strongly recommends that you do not use the account associated with the root user in BHOLD Core (by default, the account used to install BHOLD Core). This account can be the same account that you use to connect to FIM, however.||Write the user account name here:|
|Password||Specifies the password of the user account specified in User.||Write the password here: Important: Be sure to keep this password in a hidden, secure location.|
|IP/Machine Address||Specifies the IP address of the BHOLD Core website server. Do not use the server name.||Write the IP address here:|
|Port number||Specifies the port number of the BHOLD Core website.||Write the port number here:|
To install the BHOLD FIM Integration module, log on as a member of the Domain Admins group, download the following file and run it as administrator on the server that you intend to install the BHOLD FIM Integration module on:
Replace <Version> with the version number of the BHOLD FIM Integration release that you are installing.
To run the program file as an administrator, right-click the file and then click Run as administrator.
After installing BHOLD FIM Integration, you must configure Microsoft SharePoint to give the BHOLD service account site-owner permissions. Also, if the FIM Portal is configured to use Secure Sockets Layer (SSL) security, you must modify files that contain references to the addresses of BHOLD pages added to the FIM Portal.
To function properly, BHOLD FIM Integration requires the BHOLD service account to have site-member permissions in Microsoft SharePoint.
Log on to the server running BHOLD FIM Integration with administrator privileges.
Click Start, and then click Internet Exporer.
In the address bar, type
https://localhostif SharePoint is configured to use SSL security, otherwise type
On the left side of the Team Site page, click People and Groups.
Under Groups click Team Site Members, and in the center-pane toolbar, click New, and then click Add Users.
On the Add Users: Team Site page, in Users/Groups, type
BHOLDApplicationGroup, and then click the Check Names button under the Users/Groups box. The group name should resolve to include the domain name.
Click Give users permissions directly, select Full Control – Has full control, and then click OK.
Verify that BHOLDApplicationGroup is listed in Permissions: Team Site, and then close Internet Explorer.
If the FIM Portal is configured to use SSL security, you must modify files on the FIM server so that links to BHOLD pages will open. The files are located in the following folder: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\BHOLD.
The following table lists the files and the original and changed versions of the strings to be edited.
|File||Original string||Changed String|
<BHOLD_Server> specifies the name of the BHOLD server as found in the original version of the file
<FIM_Server> specifies the name of the FIM server as found in the original version of the file
<BHOLD_Server_FQDN> specifies the fully qualified domain name (FQDN) of the BHOLD server
<FIM_Port> specifies the port number of the FIM server as found in the original version of the file
<FIM_Server_FQDN> specifies the FQDN of the FIM server
<FIM_SSL_Port> specifies a different port for use with SSL on the FIM server
When FIM and BHOLD are integrated for self-service, the workflows for approvals are run in the FIM Service. This is similar to the workflow model for requests that originate in the FIM Portal, such as when a user submits a request to join a distribution list. There are key differences between BHOLD role workflows and other workflows hosted in the FIM Service, however. In the case of BHOLD, workflow parameters that specify which users must approve a role request originate in BHOLD, rather than being stored in the workflow definitions in the FIM Service database. These parameters are provided to the FIM Service by BHOLD when the first request is made, and an action workflow communicates the results back to BHOLD Core.
BHOLD selects an approver for a self-service request in one of three ways:
Line manager as approver: role-based selection for an organizational unit (orgunit)
If a role has an attribute named roletype that is set to Approver or Escalator, and if that role is linked to one or more users in the context of an orgunit, requests from users within that orgunit must be approved by one of the users that is linked to the role with the Approver or Escalator roletype.
Line manager as approver: attribute-based selection for an orgunit
Each orgunit can have one or more attributes that specify the aliases of users who can approve role assignments for other users in the orgunit. These attributes are named approver1, approver2, and so on. When a user in the orgunit requests a role assignment, BHOLD routes the request (through FIM) to the users specified by the orgunit approver attributes. If an orgunit does not have any of these attributes set, BHOLD checks parent orgunits up to the root orgunit.
Role manager as approver: attribute-based selection for a role
A role can have one or more attributes (also named approver1, and so on) that specify the aliases of users who can approve the assignment of the role. When a user requests to be assigned a role that has these approver attributes set, BHOLD routes the request to the users specified by the attributes.
If an approver for a self-service role request is not specified by one of these methods, by default BHOLD automatically assigns the role without requiring approval. For this reason, immediately after installing BHOLD FIM Integration, you should configure the root orgunit with the alias of an approver, such as the root account. This will prevent a user from unintentionally being granted a role before a more comprehensive approval policy can be implemented.
Log on to the BHOLD Core server as an administrator.
Click Start, and then click Internet Explorer.
In the Internet Explorer address bar, type
http://localhost:5151/bhold/core, and then press the Enter key.
On the BHOLD Core home page, under Attribute def, click Attribute types.
On the Attribute type page, click Add.
On the Add attribute type page, in Identity, type
approver1, in the Data type list, click AlphaNumeric, in Maximum length, type
255, in List of values, click No, in English, type
Approver 1, click OK, and then click Done.
In the left pane, under Attribute def click Attribute type sets.
On the Attribute type sets page, click Add.
On the Add attribute type set page, in Description, type
Orgunit Attributes, and then click OK.
On the Orgunit Attributes page, expand Attribute types, and then click Modify.
In the Attribute type list, click approver1, click Add, and then click Done.
In the left pane, click Object types.
On the Object types page, click OrgUnit.
On the Object type/OrgUnit page, expand Attribute type sets, and then click Modify.
On the Link attribute type set/OrgUnit page, in Order, type
10, in the Attribute type set list, click Orgunit Attributes, click Add, and then click Done.
In the left pane, under Model, click Organizational units.
On the Organizational units page, click root.
On the Organizational unit/root page, click Modify.
On the Modify organizational unit attributes/root page, in Approver, type the domain and user name of the user who will approve role-assignment requests, in the format <domain>
\<user>, where <domain> is the NetBIOS (short) domain name and <user> is the user’s logon name.
The domain and user name must match the default alias of a user in the BHOLD Core database.
As an alternative to specifying an approver for organizational units, you can specify an approver for proposed roles in the BHOLD Core database. To do so, create the approver1 attribute, add it to an attribute typeset associated with the Role object type, and then modify each proposed role to specify the approver.
To provide better workflow security, in addition to approvers, you should designate additional approval modes and users by creating and populating the following attributes for orgunits and roles:
where <n> indicates an optional numerical suffix to provide multiple attributes of the same type.
BHOLD FIM Integration installation creates sets, workflow definitions, and Management Policy Rules (MPRs) to the FIM Service. If you had customized your FIM deployment to change the sets of administrators or the sets of users who can make requests, you should ensure that the MPRs reference the correct user sets.
Before users of the FIM Portal can use the self-service features provided by BHOLD, the users’ accounts must be synchronized into the BHOLD database from the FIM Synchronization Service. In particular, there must be a user record in the BHOLD Core database and in the FIM Service database for each user who can make a self-service request or is specified as an approver or escalator for self-service requests.
If you have not already done so, you must install the Access Management Connector module to perform this synchronization. For more information, see Access Management Connector Installation.