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

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 Integrations > Connectors and click Add connector.

2. Search for FloQast and click Add.

3. Choose how to set up the new FloQast 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 C1)

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

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

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

7. Enter the configuration information from the previous section.

8. Click Save.

9. 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 Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new FloQast 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 C1)

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

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

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

7. 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.