Nailing the Security Audit with RRCU

ConductorOne docs

Set up a Formal connector

ConductorOne provides identity governance and just-in-time provisioning for Formal. Integrate your Formal instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

  • Sync user identities from Formal to ConductorOne

  • Resources supported:

    • Groups
  • Provisioning supported:

    • Group membership

Add a new Formal connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, click Connectors > Add connector.

  2. Search for Formal and click Add.

    Don’t see the Formal connector? Reach out to support@conductorone.com to add Formal to your Connectors page.

  1. Choose how to set up the new Formal connector:

    • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

    • Add the connector to a managed app (select from the list of existing managed apps)

    • Create a new managed app

    Do you SSO into Formal using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Formal app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

  1. Set the owner for this connector. You can manage the connector yourself, or choose someone else. Setting multiple owners is allowed.

    A Formal connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Ability to generate API keys in Formal
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your Formal connector.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Formal connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and the ability to generate API keys in Formal must perform this task.

Step 1: Generate a Formal API key

  1. Sign into Formal and click the API Keys tile.

  2. Click Create API Key.

  3. Give the new key a name, such as “ConductorOne integration”.

  4. Click Create. The new API key is generated.

  5. Carefully and copy and save API key. We’ll use it in Step 2.

Step 2: Add your Formal credentials to ConductorOne

  1. In ConductorOne, navigate to the Formal connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Connectors > Formal (if there is more than one Formal listed, click the one with your name listed as owner and the status Not connected).

  2. Find the Settings area of the page and click Edit.

  3. Paste the API key you generated in Step 1 into the API key field.

  4. Click Save.

  5. The connector’s label changes to Syncing, followed by Connected. View the logs to ensure that information is syncing.

That’s it! Your Formal connector is now pulling access data into ConductorOne.

Configure the Formal integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Formal and ConductorOne.

See the ConductorOne Formal integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.