IDology is an ID verification service that can be used to verify identification provided by users.
The IDology integration is comprised of the following components:
-
Azure AD B2C – The authorization server, responsible for verifying the user’s credentials. It is also known as the identity provider
-
IDology – The IDology service takes inputs provided by the user and verifies the user’s identity
-
Custom Rest API – This provided API implements the integration between Azure AD and the IDology service.
When you are ready to get an IDology account, sign up at xxxx
Deploy the provided API code to an Azure service. The code can be published from Visual Studio, following these instructions.
Note the URL of the deployed service. This will be needed to configure Azure AD with the required settings.
Application settings can be configured in the App service in Azure. This allows for settings to be securely configured without checking them into a repository. The Rest API needs the following settings provided:
| Application Setting Name | Source | Notes |
|---|---|---|
| IdologySettings:ApiUsername | IDology account configuration | |
| IdologySettings:ApiPassword | IDology account configuration | |
| WebApiSettings:ApiUsername | Define a username for the API | This will be used in the ExtId configuration |
| WebApiSettings:ApiPassword | Define a password for the API | This will be used in the ExtId configuration |
The provided sample policy is based on the
Following this documentation, create two policy keys – one for the API Username, and one for the API password which you defined above.
The sample policy uses these key names:
-
B2C_1A_RestApiUsername
-
B2C_1A_RestApiPassword
In the section “Idology-ExpectId-API”, update the ServiceUrl metadata item with the location of the API deployed above.
Follow this documentation to configure the policy for the B2C tenant.
This sample policy is based on LocalAccounts starter pack.