Capabilities
The Confluence Data Center connector supports automatic account provisioning.
This connector does not support account deprovisioning. You must deprovision accounts directly in Confluence Data Center.
Gather Confluence Data Center credentials
Configuring the connector requires you to pass in credentials generated in Confluence Data Center. Gather these credentials before you move on.
ImportantA user with Administrator access in Confluence Data Center must perform this task.
Create an API token
Log into your Confluence Data Center account with Administrator access.
Give your token a label, such as C1, and click Create.
Carefully copy and save the newly generated API token.
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in C1
- Access to the set of Confluence Data Center credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.Cloud-hosted connector not currently available.
Follow these instructions to use the Confluence Data Center 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
- GitHub repository: Access the source code, report issues, or contribute to the project.
Step 1: Set up a new Confluence Data Center connector
In C1, navigate to Integrations > Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Confluence Data Center 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
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.
In the Settings area of the page, click Edit.
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 Confluence Data Center connector deployment:Secrets configuration
See the connector’s README or run --help to see all available configuration flags and environment variables.Deployment configuration
Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
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 Confluence Data Center connector to. Confluence Data Center data should be found on the Entitlements and Accounts tabs.
