Set up FloQast connector

C1 provides identity governance for FloQast. Integrate your FloQast instance with C1 for unified visibility and governance over user access.

Capabilities

Resource	Sync	Provision
Account
Account Role
Audit Project Role
Group

The connector syncs each user’s account role and audit project role, and syncs user groups along with their owners, so all four can be included in access reviews and access policies.

Additional functionality:

None.

Gather FloQast configuration information

Configuring the connector requires you to pass in information from FloQast. Gather these configuration details before you move on.

Here’s the information you’ll need:

• API Key

See the FloQast docs for information on how to acquire credentials: View the documentation

Configure the FloQast connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of FloQast configuration information gathered by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for FloQast and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. Enter the configuration information from the previous section.

9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your FloQast connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the FloQast connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new FloQast connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your FloQast connector deployment:

Secrets configuration

# baton-floqast-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-floqast-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # FloQast config
  BATON_FLOQAST_API_KEY: <API Key for FloQast>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-floqast.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-floqast
  labels:
    app: baton-floqast
spec:
  selector:
    matchLabels:
      app: baton-floqast
  template:
    metadata:
      labels:
        app: baton-floqast
        baton: true
        baton-app: floqast
    spec:
      containers:
      - name: baton-floqast
        image: public.ecr.aws/conductorone/baton-floqast:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-floqast
        envFrom:
        - secretRef:
            name: baton-floqast-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the floqast connector to. floqast data should be found on the Entitlements and Accounts tabs.

Done. Your FloQast connector is now pulling access data into C1.