Edit

Share via

Tutorial: Configure Azure Active Directory B2C with the Arkose Labs platform

  • Article

In this tutorial, learn how to integrate Azure Active Directory B2C (Azure AD B2C) authentication with the Arkose Labs Arkose Protect Platform. Arkose Labs products help organizations against bot attacks, account takeover, and fraudulent account openings.

Prerequisites

To get started, you'll need:

Scenario description

Arkose Labs products integration includes the following components:

  • Arkose Protect Platform - A service to protect against bots and other automated abuse
  • Azure AD B2C sign-up user flow - The sign-up experience that uses the Arkose Labs platform
    • Custom HTML, JavaScript, and API connectors integrate with the Arkose platform
  • Azure Functions - Your hosted API endpoint that works with the API connectors feature

The following diagram illustrates how the Arkose Labs platform integrates with Azure AD B2C.

Diagram of the Arkose Labs platform and Azure AD B2C integration architecture.

  1. A user signs up and creates an account. The user selects Submit, and an Arkose Labs enforcement challenge appears.
  2. The user completes the challenge. Azure AD B2C sends the status to Arkose Labs to generate a token.
  3. Arkose Labs sends the token to Azure AD B2C.
  4. Azure AD B2C calls an intermediate web API to pass the sign-up form.
  5. The sign-up form goes to Arkose Labs for token verification.
  6. Arkose Labs sends verification results to the intermediate web API.
  7. The API sends a success or failure result to Azure AD B2C.
  8. If the challenge is successful, a sign-up form goes to Azure AD B2C, which completes authentication.

Request a demo from Arkose Labs

  1. Go to arkoselabs.com to book a demo.
  2. Create an account.
  3. Navigate to the Arkose Portal sign-in page.
  4. In the dashboard, navigate to site settings.
  5. Locate your public key and private key. You'll use this information later.

Note

The public and private key values are ARKOSE_PUBLIC_KEY and ARKOSE_PRIVATE_KEY. See, Azure-Samples/active-directory-b2c-node-sign-up-user-flow-arkose.

Integrate with Azure AD B2C

Create an ArkoseSessionToken custom attribute

To create a custom attribute:

  1. Sign in to the Azure portal, then navigate to Azure AD B2C.
  2. Select User attributes.
  3. Select Add.
  4. Enter ArkoseSessionToken as the attribute Name.
  5. Select Create.

Learn more: Define custom attributes in Azure Active Directory B2C

Create a user flow

The user flow is for sign-up and sign-in, or sign-up. The Arkose Labs user flow appears during sign-up.

  1. Create user flows and custom policies in Azure Active Directory B2C. If using a user flow, use Recommended.

  2. In the user flow settings, go to User attributes.

  3. Select the ArkoseSessionToken claim.

    Screenshot of the Arkose Session Token under User attributes.

Configure custom HTML, JavaScript, and page layout

  1. Go to Azure-Samples/active-directory-b2c-node-sign-up-user-flow-arkose.
  2. Find the HTML template with JavaScript <script> tags. These do three things:

  • Load the Arkose Labs script, which renders their widget and does client-side Arkose Labs validation.

  • Hide the extension_ArkoseSessionToken input element and label, corresponding to the ArkoseSessionToken custom attribute.

  • When a user completes the Arkose Labs challenge, the user response is verified and a token generated. The callback arkoseCallback in the custom JavaScript sets the value of extension_ArkoseSessionToken to the generated token value. This value is submitted to the API endpoint.

    Note

    Go to developer.arkoselabs.com for Client-Side Instructions. Follow the steps to use the custom HTML and JavaScript for your user flow.

  1. In Azure-Samples, modify selfAsserted.html file so <ARKOSE_PUBLIC_KEY> matches the value you generated for the client-side validation.

  2. Host the HTML page on a Cross-Origin Resource Sharing (CORS) enabled web endpoint.

  3. Create a storage account.

  4. CORS support for Azure Storage.

    Note

    If you have custom HTML, copy and paste the <script> elements onto your HTML page.

  5. In the Azure portal, go to Azure AD B2C.

  6. Navigate to User flows.

  7. Select your user flow.

  8. Select Page layouts.

  9. Select Local account sign up page layout.

  10. For Use custom page content, select YES.

  11. In Use custom page content, paste your custom HTML URI.

  12. (Optional) If you use social identity providers, repeat steps for Social account sign-up page.

    Screenshot of Layout name options and Social account sign-up page options, under Page layouts.

  13. From your user flow, go to Properties.

  14. Select Enable JavaScript.

Learn more: Enable JavaScript and page layout versions in Azure Active Directory B2C

Create and deploy your API

This section assumes you use Visual Studio Code to deploy Azure Functions. You can use the Azure portal, terminal, or command prompt to deploy.

Go to Visual Studio Marketplace to install Azure Functions for Visual Studio Code.

Run the API locally

  1. In Visual Studio code, in the left navigation, go to the Azure extension.
  2. Select the Local Project folder for your local Azure Function.
  3. Press F5 or select Debug > Start Debugging. This command uses the debug configuration Azure Function created.
  4. Azure Function generates files for local development, installs dependencies, and the Function Core tools, if needed.
  5. In the Visual Studio Code Terminal panel, output from the Function Core tool appears.
  6. When the host starts, select Alt+click on the local URL in the output.
  7. The browser opens and runs the function.
  8. In the Azure Functions explorer, right-click the function to see the locally hosted function URL.

Add environment variables

The sample in this section protects the web API endpoint when using HTTP Basic authentication. Learn more on the Internet Engineering Task Force page RFC 7617: The Basic Authentication.

Username and password are stored as environment variables, not part of the repository. Learn more on Code and test Azure Functions locally, Local settings file.

  1. In your root folder, create a local.settings.json file.
  2. Copy and paste the following code onto the file:
{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "",
    "FUNCTIONS_WORKER_RUNTIME": "node",
    "BASIC_AUTH_USERNAME": "<USERNAME>",
    "BASIC_AUTH_PASSWORD": "<PASSWORD>",
    "ARKOSE_PRIVATE_KEY": "<ARKOSE_PRIVATE_KEY>",
    "B2C_EXTENSIONS_APP_ID": "<B2C_EXTENSIONS_APP_ID>"
  }
}
  1. The BASIC_AUTH_USERNAME and BASIC_AUTH_PASSWORD are the credentials to authenticate the API call to your Azure Function. Select values.
  • <ARKOSE_PRIVATE_KEY> is the server-side secret you generated in the Arkose Labs platform.
    • It calls the Arkose Labs server-side validation API to validate the value of the ArkoseSessionToken generated by the front end.
    • See, Server-Side Instructions.
  • <B2C_EXTENSIONS_APP_ID> is the application ID used by Azure AD B2C to store custom attributes in the directory.

  1. Navigate to App registrations.

  2. Search for b2c-extensions-app.

  3. From the Overview pane, copy the Application (client) ID.

  4. Remove the - characters.

    Screenshot of the display name, application ID, and creation date under App registrations.

Deploy the application to the web

  1. Deploy your Azure Function to the cloud. Learn more with Azure Functions documentation.

  2. Copy the endpoint web URL of your Azure Function.

  3. After deployment, select the Upload settings option.

  4. Your environment variables are uploaded to the Application settings of the app service. Learn more on Application settings in Azure.

    Note

    You can manage your function app. See also, Deploy project files to learn about Visual Studio Code development for Azure Functions.

Configure and enable the API connector

  1. Create an API connector. See, Add an API connector to a sign-up user flow.

  2. Enable it for your user flow.

    Screenshot of Display name, Endpoint URL, Username, and Password on Configure and an API connector.

  • Endpoint URL - The Function URL you copied while you deployed Azure Function
  • Username - The username you defined
  • Password - The password you defined

  1. In the API connector settings for your user flow, select the API connector to be invoked at Before creating the user.

  2. The API validates the ArkoseSessionToken value.

    Screenshot of the entry for Before creating the user, under API connectors.

Test the user flow

  1. Open the Azure AD B2C tenant.
  2. Under Policies, select User flows.
  3. Select your created user flow.
  4. Select Run user flow.
  5. For Application select the registered app (the example is JWT).
  6. For Reply URL, select the redirect URL.
  7. Select Run user flow.
  8. Perform the sign-up flow.
  9. Create an account.
  10. Sign out.
  11. Perform the sign-in flow.
  12. Select Continue.
  13. An Arkose Labs puzzle appears.

Resources