Page Comparison

EmpowerID offers a connector specifically designed for Azure AD B2C integration. Administrators can utilize this connector to establish a seamless connection between EmpowerID and their Azure AD B2C system. This connection creates an account store within the EmpowerID Identity Warehouse, serving as a central hub for configuring how EmpowerID manages identity information within the Azure AD B2C system.

Info

Prerequisites

Administrative access to the Azure AD B2C.

Administrative access to EmpowerID.

Step 1 - Gathering Necessary Information & Configuring the B2C Tenant

Configure the B2C Tenant

Before you begin creating an Account Store and connecting to a B2C tenant, the following steps must be completed in the client environment. Read the overview document to understand the components and how they work, which will give you more insight into the relevance of the steps.

Tip
Necessary permissions are automatically configured during the microservice deployment from EmpowerID. The information below is for administrative and troubleshooting purposes only. Please skip if you only want to create an account store.

Register an App in B2C Tenant:
- An application should be registered with the client Azure as a B2C tenant.
Create a Certificate:
- Generate a certificate from the Azure application that you created. This certificate needs to be uploaded to EmpowerID for configuration purposes. It will be used to authenticate requests from EmpowerID to the application. The certificate will be stored in a key vault located in the B2c tenant where the SCIM Microservice is deployed in Azure.
Assign Application Roles and Permissions:
- Roles: The Help Desk Administrator role should be enabled. This role, which involves managing and supporting user-related issues within the Azure AD B2C environment, should be configured in the Azure AD B2C tenant.
- Graph API Permissions: Please also provide the permissions that should be enabled for the Graph API in the app created for the Azure AD B2C Tenant. The list of permissions is provided below.

Expand

title	List of permissions needed for Graph API

Following is the list of the permissions that should be enabled in the app created for the Azure AD B2C Microservice.

AuditLog.Read.All
Directory.Read.All
Group.Create
Group.Read.All
Group.ReadWrite.All
offline_access
openid
User.EnableDisableAccount.All
User.Export.All
User.Invite.All
User.ManageIdentities.All
User.Read.All
User.ReadWrite.All
UserAuthenticationMethod.Read.All
UserAuthenticationMethod.ReadWrite.All

Gather Necessary Information

To configure Azure AD B2C in EmpowerID, you'll need the following information ready for configuration.

Attribute	Component	Description
Azure App Service URL	SCIM Microservice Deployed in Azure	This attribute refers to the URL of the SCIM (System for Cross-domain Identity Management) microservice endpoint hosted on Azure App Service. The URL is provided by the EmpowerID DevOps teams and points to where the microservice is deployed. This URL does not include the prefix v1.0 as part of the path.
Application ID	The client application configured in the microservice tenant to access the microservice.	This attribute refers to the Application ID of the client application that is configured in the microservice's tenant. This Application ID is used to grant the client application access to the SCIM microservice. The Application ID is provided by the DevOps teams, and it is essential for authentication and authorization purposes.
Azure App Certificate Thumbprint	SCIM Microservice Deployed in Azure	This attribute refers to the thumbprint of the certificate used by the SCIM microservice deployed in Azure. The thumbprint is a unique identifier of the certificate that is required to establish secure communication between the client application and the microservice. The client application, which is configured in the microservice tenant, uses this thumbprint to access the microservice securely. The DevOps teams provide this thumbprint.
B2C App Service Tenant ID	B2C App Service Tenant ID	The B2C App Service Tenant ID is the unique identifier for a specific Azure B2C instance. It can be retrieved by accessing the Azure B2C instance associated with the client's tenant.
Azure AD B2C Tenant FQDN	B2C tenant FQDN.	Azure AD B2C Tenant FQDN typically refers to the tenant name or the UPN suffix of the client's B2C tenant in Azure. This Fully Qualified Domain Name (FQDN) uniquely identifies the B2C tenant within the Azure environment.

Step 2 – Create an account store for Azure AD B2C

Once you have set up Azure and published the EmpowerID Azure AD B2C SCIM microservice to your Azure tenant, you will need to connect EmpowerID to the tenant. This connection will allow that allows the tenant's user and group information to be brought into EmpowerID, where it can be easily managed and synchronized with data in any connected back-end user directories. Please follow the instructions below to create an account store for your organization’s Azure AD B2C instance, within EmpowerID.

Log in to the EmpowerID portal.
On the navbar, expand Admin → Applications and Directories and click Account Stores and Systems.
Select the Account Stores tab and click on the Create Account Store link.
Please search Search for and choose select the Azure AD B2C SCIM account store from the System Types menu to continue. Once selected, then click on the submit button Submit.
Please provide Provide the following information related to for the account store and click on submit to create the account store. Submit:
- Account Store Name: Provide a unique and descriptive name for the account store.
- Azure App Service URL: URL for the Microservice EndPoint of EID.( do not prefix v1.0)
- Application ID: The client application configured in the microservice tenant to access the microservice.
- Azure App Certificate Thumbprint: Upload the certificate to the EID portal and provide its thumbprint.
- B2C App Service Tenant ID: The ID of the tenant where the microservice is deployed.
- Azure AD B2C Tenant FQDN: The fully qualified domain name (FQDN) of the B2C tenant.
  Image Modified

EmpowerID creates the Azure AD B2C account store and the associated resource system. The next step is to verify the resource system parameters match your tenant information.

Step

2

3 – Verify Resource System Parameters

Tip
Please note that the values for `ApplicationID`, `AuthCertificateThumbprint`, and `TenantID` are encrypted and that you will not see the values in the user interface.

Navigate to the Admin > Applications and Directories > Account Stores and Systems, and Select select the Account Stores tab, as mentioned in the previous step.
Kindly search for and select your previously created account storeSearch for the Azure AD B2C SCIM account store you created and click the Account Store link for it.
This
directs you to On the Account Store and Resource System page that appears, select the Resource System tab and expand the Configuration Parameters accordion.
Image Added
Verify the following parameters are correct:

Configuration Item	Description
AccessTokenUrl	URL endpoint for obtaining an access token from the Azure AD

account store EmpowerID created for the tenant. This page contains several tabs related to the account store that you can access to view and manage the account store and resource system.

Image RemovedSelect the Resource System tab, find and expand the Configuration Parameters accordion at the bottom of the page.

Image RemovedVerify the following parameters are correct for your account store.
Insert excerptIL:Azure AD B2C Scim ComponentsIL:Azure AD B2C Scim Componentsnameresourcetablenopaneltrue

tenant where the microservice is deployed.
AuthorizationProviderFullAssemblyName	Fully qualified assembly name of the authentication provider for the microservice.
AuthorizationProviderType	Type of the authorization provider for the microservice.
AuthorizationUrl	URL for token authorization.
AzureAppID	Application ID in Azure configured to access the microservice.
AzureTenantID	Tenant ID where the microservice is deployed.
certificateThumbPrint	Thumbprint of the certificate configured for accessing the microservice.
CreateGroupUrl	URL for creating a new group in the microservice.
CreateOrUpdateGroupJsonTemplate	JSON template for creating or updating a group.
CreateOrUpdateUserJsonTemplate	JSON template for creating or updating a user.
CreateUserUrl	URL for creating a new user in the microservice.
ExternalSysSupportGetDeleted	Indicates whether the microservice supports querying deleted items.
ExternalSystemSupportIncrementalMember	Indicates whether the microservice supports incremental membership inventory.
GetAllDeletedGroupsUrl	URL for retrieving all deleted groups from the microservice.
GetAllDeletedUsersUrl	URL for retrieving all deleted users from the microservice.
GetDeleteorUpdateGroupByIdUrl	URL for retrieving, deleting, or updating a group by its ID.
GetDeleteorUpdateUserByIdUrl	URL for retrieving, deleting, or updating a user by its ID.
GetGroupMemberUrl	URL for querying members of a group in the microservice.
GetGroupOwnerUrl	URL for querying owners of a group in the microservice.
GetNewOrUpdatedGroupsUrl	URL for retrieving newly created or updated groups from the microservice within a specific time range.
GetNewOrUpdatedUsersUrl	URL for retrieving newly created or updated users from the microservice within a specific time range.
GroupTypeMapping	JSON defining the mapping between source group types and EID’s group types.
IdentiityIssuer	Issuer that assigns identities for users created from the EID Portal.
IsIncrementalInventory	Indicates whether the microservice supports incremental inventory.
IsPagedUsingToken	Indicates if paging supports skipToken.
MembershipInboxGroupPageSize	Group page size for membership inventory during initial load.
MembershipInboxMemberPageSize	Page size for group inventory during initial load.
MembershipInboxParallelProcessingThreshold	Threshold for parallel processing of group membership during initial load.
PageSize	Page size used when running a full inventory.
QueryGroupsUrl	URL for querying groups in the microservice with pagination support.
QueryUsersUrl	URL for querying users in the microservice with pagination support.
resetUserPasswordUrl	URL for requesting a password reset for a user in the microservice.
Scope	Scope specified when retrieving a token using OAuth authentication.
ServiceUrl	Endpoint URL of the microservice.

To edit the value of a parameter, click the Edit button for the parameter you want to edit.
Image Modified
Enter the new value in the Value field and click Save.

After updating the Configuration Parameters, the next step is configuring the Attribute Flow.

Step

3

4 – Configure Attribute Flow

Insert excerpt

	IL:Configure Attribute Flow Rules-V21
	IL:Configure Attribute Flow Rules-V21
nopanel	true

Now that you have set up the attribute flow in EmpowerID, the next steps involve configuring the account store and enabling EmpowerID to inventory it.

Step

4

5 – Configure Account Store Settings

Navigate to the Admin > Applications and Directories > Account Stores and Systems, and Select select the Account Stores tab, as mentioned in the previous topics.
Please search and open the details page of the account store that was previously created.
You will be directed to the edit page by clicking the "Edit" link for the account store. This page provides you with the settings to define the desired approach for EmpowerID's management of user information discovered in your Azure tenant during the inventory process. The table below the image contains detailed descriptions of the settings pertaining to the account storeSearch for the Azure AD B2C account store you created and click the Account Store link to navigate to the details page for it.
Click the Edit (pencil icon) link to put the account store into edit mode.
Review the account store settings and adjust them as necessary, then click "Save" upon completion.

Insert excerpt
IL:Azure AD Account Store Settings V22
IL:Azure AD Account Store Settings V22
nopanel true
Configure the account stores setting as needed and click on Save.

Step

5

6 – Enable the Account Inbox Permanent Workflow

Insert excerpt

	IL:Enable Account Inbox PW - V22
	IL:Enable Account Inbox PW - V22
nopanel	true

Step

6

7 – Enable / Disable Inventory & Component Jobs

The connector includes two additional component jobs, namely GroupOwnershipFullInventory and GroupMembershipFullInventory, in addition to the default inventory job. To ensure the inventory runs properly, follow these steps in the correct order:

Disable Incremental Inventory
- Set IsIncrementalInventory to False.
Disable Component Jobs
- Navigate to the Account Store Details page for the account store.
- Scroll to the Additional Jobs Per System section.
- Click the link under the Display Name column for each component job.
- On the inventory details page for each job, uncheck the Is Enabled checkbox to disable the inventory for that component job.
- Click Save.
Enable and Execute Default Inventory Job
- Return to the Account Store Details page for the account store.
- Click the Edit link to enter edit mode.
- Select the Inventory tab.
- Enter the job's start and end dates in the Start and Stop fields, respectively.
- Select the desired inventory interval (default is every 10 minutes).
- Check Inventory Enabled.
- Click Save.
- Ensure that the job runs successfully.
Run Additional Component Jobs
- Run the GroupOwnershipFullInventory and GroupMembershipFullInventory jobs.
- Wait until these component jobs have successfully completed.
Re-enable Incremental Inventory
- Set IsIncrementalInventory to True.
Activate Inventory Functionality
- Ensure all inventory functionalities are active.

By following these steps, you will ensure that the inventory process for the Azure AD B2C connector runs smoothly and efficiently.

Monitoring Inventory

You can monitor the inventory of users and groups from the Users and Groups tabs of the Account Store Details page. It generally takes three iterations of the inventory job before it is successful.

Page Properties

hidden	true

Tip

The connector has two extra component jobs, namely GroupOwnershipFullInventory and GroupOwnershipFullInventory, in addition to the default inventory job. For the inventory to run properly for the connector, please make sure the actions are performed in right order,

Disable the incremental inventory feature by setting IsIncrementalInventory to False.
Disable the component jobs.
Enable and Execute the default inventory job.
Run the two additional component jobs, namely GroupOwnershipFullInventory and GroupOwnershipFullInventory, associated with the connector and wait until the component jobs have successfully completed.
Enable the incremental inventory feature by setting IsIncrementalInventory to True.
Activate the inventory functionality for the connector.

Disable the Component Job

Return to the Account Store Details page for the account store following the same steps mentioned in previous sections.
Please navigate to the bottom of the page and locate the "Additional Jobs Per System" section. Then, click on the link under the "Display Name" column for the first component job.

Image Removed

Image Added
You will be directed to the inventory details page for the job. Now, uncheck the Is Enabled checkbox to disable the inventory for the component job. Please make sure you click the Save button at the bottom of the page.

Image Removed

Image Added
Please follow the same steps to disable the second component job as well.

Enable the Full Inventory

Return to the Account Store Details page for the account store following the same steps mentioned in previous sections.
Click the Edit link to put the account store in edit mode.

Image Removed

Image Added
Select the Inventory tab and enter the job's start and end dates in the Start and Stop fields, respectively.
Select the desired inventory interval. The default interval is once every 10 minutes.
Check Inventory Enabled.
Click Save.
Ensure that the job runs successfully.

Note
Please be reminded to enable the component inventory after completing the entire inventory process successfully. Simply follow the instructions provided in the previous section but make sure to select the "Is Enabled" checkbox this time.

Step

7

8 – Recycle your EmpowerID Environment

In order to

To prevent continuous inventory errors

stating that “EnableAzureRbacInventory in system config is missing,” EmpowerID must be restarted after you have enabled inventory for the account store. The process to follow depends on whether you are running a cloud instance of EmpowerID or have an on-premise installation

, restart EmpowerID:

For Cloud Instances:

Navigate to IT Shop > Workflows.
Click Recycle Service Environment and confirm.

For On-Premise Installations:

Restart IIS.
Restart EmpowerID services.

For cloud instances

Info
Please note that this process puts the environment out of service for about 15 minutes.

On the navbar, expand IT Shop and select Workflows.
Click Recycle Service Environment.

Image Removed

Image Added
Click Yes to confirm you want to recycle the environment.

Image Removed

Image Added
Click OK.

Image Removed

Image Added

For on-premise installations

Restart IIS.
Restart the EmpowerID services.

Now that the Account Inbox Permanent workflow is turned on and inventory for the account store is enabled, you can monitor the inventory of users and groups from the Users and Groups tabs of the Account Store Details page.

Image Removed

Image Added

Info
It generally takes three iterations of the Inventory job before inventory is successful.

Div

style	float:left; position:fixed;
id	articleNav

IN THIS ARTICLE

Table of Contents

minLevel	2
maxLevel	42
minLeveloutline	2false
style	none
type	list
printable	false

Versions Compared

Old Version 15

New Version Current

Key

Step 1 - Gathering Necessary Information & Configuring the B2C Tenant

Configure the B2C Tenant

Gather Necessary Information

Step 2 – Create an account store for Azure AD B2C

Step

3 – Verify Resource System Parameters

Step

4 – Configure Attribute Flow

Step

5 – Configure Account Store Settings

Step

6 – Enable the Account Inbox Permanent Workflow

Step

7 – Enable / Disable Inventory & Component Jobs

Monitoring Inventory

Disable the Component Job

Enable the Full Inventory

Step

8 – Recycle your EmpowerID Environment

For Cloud Instances:

For On-Premise Installations:

For cloud instances

For on-premise installations