Before connecting EmpowerID to an external directory, please review the Getting Started with Directory Systems topic. The topic walks you through the prerequisites you need to complete before connecting to an external directory for the first time. These prerequisites include:
Configuring the appropriate server roles for your EmpowerID servers
Reviewing the Join and Provision Rules for your environment
Reviewing the Join and Provision Filters for your environment
If you have already connected EmpowerID to another external directory, you can skip the above prerequisites.
EmpowerID provides connectors for a wide range of user directories and resource systems. As an administrator, you can use these connectors to quickly connect EmpowerID to your organization's identity-aware systems and applications. When you do so, you create an account store for that application in the EmpowerID Identity Warehouse and use that account store to configure how you want EmpowerID to manage the identity information in that system.
EmpowerID includes an Amazon Web Services (AWS) connector that allows organizations to bring the data (user accounts, groups, roles and computers) in their AWS domain to EmpowerID, where it can be managed and synchronized with data in any connected back-end user directories. When EmpowerID inventories AWS, it creates an account in the EmpowerID Identity Warehouse for each Amazon user account, a computer for each Amazon computer, a group for each Amazon group, and a special group called an RBAC-Only group for each Amazon role.
In order to connect EmpowerID to AWS, you must have an AWS domain with an account that EmpowerID can use to connect to AWS. (EmpowerID recommends using a dedicated service account.) At a minimum, this account must have a policy with permission to read the user, group and computer data in AWS. If you plan to use EmpowerID to provision, deprovision and modify this data in AWS, the profile needs to have create, update and delete permissions as well. In addition, you must provide EmpowerID with the following information:
Access Key ID for the service account
Secret Access Key for the service account
AWS Site Name
Error rendering macro 'excerpt-include' : No link could be created for 'Connecting to Active Directory'.
Configuring EmpowerID settings for the account store connection, including whether to provision EmpowerID Persons during inventory or in batches using the Account Inbox permanent workflow (recommended).
Reviewing and configuring the attribute flow rules for the account store.
Turning on inventory.
Enabling the Account Inbox Permanent Workflow when ready—if you are using batch processing to provision Person objects from the inventoried user accounts. This is the recommended method.
Create an account store for AWS
In the navigation sidebar, expand Admin, then Applications and Directories, and click Account Stores and Systems.
Click the Actions tab, and then click the Create Account Store action.
Select Amazon AWS from the list of system types and click Submit.
On the AWS Settings page that appears, enter settings to connect to your Amazon instance to allow EmpowerID to discover and connect to it.
Site Name-The address of your AWS site
Client Key- The Access Key ID generated by Amazon for the service account
Client Secret- The Secret Access Key generated by Amazon for the service account
Tenant ID - The Tenant ID for your AWS site
EmpowerID creates the account store and the associated resource system. The next step is to configure the attribute flow between the account store and EmpowerID.
EmpowerID supports the configuration of attribute synchronization rules for flowing attribute changes between directories and the EmpowerID Identity Warehouse. Attribute Flow rules are visually configured and are always relative to the relationship between an attribute in a directory and the corresponding attribute in the EmpowerID Identity Warehouse. Attribute Flow rules define the specific fields and attributes that are synchronized between the EmpowerID Identity Warehouse person objects and the external user accounts to which they are linked. Additionally, Attribute Flow rules can be weighted by account store. For example, if you have connected EmpowerID to an HR system as well as Active Directory, and you want any changes made to an attribute in the HR system to take priority over changes made in Active Directory or EmpowerID (while allowing changes to be made in any system), you would give a higher score for each CRUD operation originating from the HR account store and correspondingly lower scores for the Active Directory account store.
The following flow rules are available:
No Sync ( Red Circle) — When this option is selected, no information flows between EmpowerID and the native system.
Bidirectional Flow (Bidirectional Green Arrow) — When this option is selected, changes made within EmpowerID update the native system and vice-versa. For most attributes, this is the default setting.
Account Store Changes Only (Left Pointing Arrow) — When this option is selected, changes can only be made in the native system and are then passed to EmpowerID.
EmpowerID Changes Only (Right Pointing Arrow) — When this option is selected, changes can only be made in EmpowerID and are then passed to the native system.
The following CRUD operations are available:
Create — This operation is used to create an attribute value for an existing attribute when the value of that attribute is null.
Update — This operation is used to update the value of an attribute.
Delete — This operation is used to delete the value of an attribute.
From the Account Stores tab of the Account Stores and Systems page, search for the account store you just created and click the Account Store link for it.
Click the Attribute Flow Rules tab to view the current rules for the account store. Please note that the attributes available depend on the account store.
To change the flow for an attribute, click the Attribute Flow drop-down located between the Person Attribute column and the External Directory Attribute column, and select the desired flow direction from the context menu.
To change the score for any of the available CRUD operations (Create, Update and Delete), enter the new score in the appropriate field. By default, scores are weighted evenly, which means that a change to an attribute originating in one connected external directory has the same authority as a change to an attribute occurring in another connected external directory.
EmpowerID only considers scores for attribute CRUD operations when multiple account stores with the same user records are connected to EmpowerID, such as would be the case if an HR System and this account store were being inventoried by EmpowerID.
Now that the attribute flow has been set, the next steps include configuring the account store and enabling EmpowerID to inventory it.
Configure account store settings
In the navigation sidebar, expand Admin, then Applications and Directories, and click Account Stores and Systems.
On the Account Stores tab, search for the account store you just created and click the link to go to its details page.
On the Account Store Details page, click the Edit button or the name of the account store.
In the edit view of the page, you can edit values in any of the enabled fields. In the General section, these are:
Display Name – Edit the name of the account store as it appears in the list of account stores.
Proxy Connection Account – Change the instance, user name, and password for the ServiceNow connection.
Account Store Proxy Shared Credential – Click in this box and press Enter to see a list of shared credentials in your system to use for the proxy connection.
Password Manager Policy – Select a password manager policy to use for the account. If not selected, it uses the Default Password Manager Policy.
Application ID – If the account store is a one-to-one match with a Tracking Only application, enter the Application Resource GUID of the application. (This value is supplied automatically if you select the Create a New Account Directory option when creating a Tracking Only application.)
Tenant ID – Enter the Tenant ID, if supplied by the connection account. (AWS uses this.)
Use Secure Binding – Toggleto bind accounts with encryption.
Show in Tree – Toggle to show the account store in the Locations tree.
Default User Creation Path – Select a location in which to create users if none is specified.
Default Group Creation Path – Select a location in which to create groups if none is specified.
EmpowerID Group Creation Path – Select a location in which to create EmpowerID groups if none is specified.
Max Accounts per Person – Enter the maximum number of user accounts from this domain that an EmpowerID Person can have linked to them. This prevents the possibility of a runaway error caused by a wrongly configured Join rule. We recommended setting this value to 1 unless users commonly have multiple accounts and you want them to be joined to the same person.
In the Features section, you can select any of these values:
Use for Authentication –
Allow Search for User Name in Authentication –
Allow Password Sync – Toggle to allow EmpowerID to sync password changes discovered during inventory.
Queue Password Changes – Toggle to have EmpowerID send password changes to the Account Password Reset Inbox for batch processing.
Queue Password Changes on Failure – Toggle to have EmpowerID send password changes to the Account Password Reset Inbox only when the change fails.
Allow Account Creation on Membership Request – Toggle to allowusers without accounts to request group membership and automatically have an account created.
Batch Calls –
Allow Attribute Flow – Toggle to allowattribute changes to flow between EmpowerID and the account store.
Allow Person Provisioning – Toggle to allow EmpowerID to create Person objects from the user records discovered during inventory.
Allow Provisioning – Toggle to allow EmpowerID to create new Groups in ServiceNow from requests discovered during inventory.
Allow Deprovisioning – Toggle to allowEmpowerID to delete Groups in ServiceNow based on requests discovered during inventory.
Automatic Person Join – Toggle to allowEmpowerID to join newly discovered accounts to people during the inventory process if they meet the Join Rule as specified by the Custom_Account_InventoryInboxJoinBulkSQL stored procedure.
Automatic Person Provision – Toggle to allowEmpowerID to provision EmpowerID people for new accounts discovered during the inventory process if they meet the Provision Rule specified by theCustom_Account_InventoryInboxGetAccountsToProvisionSQL stored procedure.
Default Provision Business Role – Set a default Business Role to assign people if none is specified.
Default Provision Location – Set a default Location to assign people if none is specified.
Allow Business Role and Location Re-Evaluation – Toggle if you have multiple account stores to manage and want to specify a priority for each.
Business Role and Location Re-Evaluation Order – Enter a number to specify the priority of the account store for determining the Business Roles and Locations to assign to a Person. Account Stores with a higher value take precedence.
Recertify All Group Changes – Toggle to allowEmpowerID to generate recertification review tasks for all changes in ServiceNow Groups.
When you have finished configuring the settings the last step is to enable EmpowerID to enable inventory. To do so, click the Inventory tab and select Enable Inventory.
When finished, click Save to save your changes.
If you are using the Account Inbox to provision or join the user accounts in AWS to Empower Persons (recommended), you need to turn on the Account Inbox. This is demonstrated below.
On the navbar, expand Infrastructure Admin> EmpowerID Server and Settings and select Permanent Workflows.
On the Permanent Workflows page, click the Display Name link for Account Inbox.
On the Permanent Workflow Details page that appears, click the pencil icon to put the workflow in edit mode.
On the navbar, expand System Logs > Policy Inbox Logs and click Account Inbox.
The Account Inbox page appears. This page provides tabbed views of all information related to processing new user accounts discovered in a connected account store during inventory. An explanation of these tabs follows.
Dashboard — This tab provides a quick summary of account inbox activity.
Not Processed — This tab displays a grid view of all inventoried user accounts not yet used to provision a new EmpowerID Person or joined to an existing Person. Any accounts that fail to meet the Join and Provision rules are displayed here as well.
Failed — This tab displays a grid view of any account joining or provisioning failures.
Ignored — This tab displays a grid view of all accounts ignored by the account inbox. Accounts are ignored if they do not qualify as user accounts.
Joined — This tab displays a grid view of all accounts joined to an EmpowerID Person. Joins occur based on the Join rules applied to the account store.
Processed — This tab displays a grid view of all accounts that have been used to either provision a new EmpowerID Person or joined to an existing EmpowerID Person.
Provisioned — This tab displays a grid view of all accounts that have been used to provision an EmpowerID Person. Provisioning occurs based on the Provision rules applied to the account store.
Orphans — This tab displays a grid view of all user accounts without an EmpowerID Person.
All — This tab displays a grid view of all user accounts and the status of those accounts in relation to the Account Inbox.
From the navigation sidebar, navigate to the Audit Log by expanding System Logs and clicking Audit Log.
Type AWS in the Search field and press ENTER. You should records for your AWS users approved by EmpowerID System.
If you have AWS groups, click the Group Membership Changes tab and search for your AWS groups. You should those groups and the group members.
From the navigation sidebar, navigate to AWS Manager by expanding Pages and clicking AWS Manager. You should see a dashboard displaying your AWS account store information.
Click through each tab of AWS Manager. You should the information relevant to that tab, as well as an Actions panel with a list of actions that you can perform against the selected resource or resource type. For example, if you select the EC2 Instances tab, you can view information about your EC2 instances, delete or disable those instances as well create new instances, among other things.