ConductorOne provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence Data Center instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
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.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Confluence Data Center credentials generated by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
Step 1: Set up a new Confluence Data Center connector
1
In ConductorOne, navigate to Connectors > Add connector.
2
Search for Baton and click Add.
3
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 ConductorOne)
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 ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne 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.
# baton-confluence-datacenter-secrets.yamlapiVersion: v1kind: Secretmetadata: name: baton-confluence-datacenter-secretstype: OpaquestringData: # ConductorOne credentials BATON_CLIENT_ID: <ConductorOne client ID> BATON_CLIENT_SECRET: <ConductorOne client secret> # Confluence Data Center credentials BATON_ACCESS_TOKEN: <Access token for your Confluence Data Center account> BATON_HOSTNAME: <URL of your Confluence Data Center instance> BATON_USERNAME: <Username for Confluence Data Center account> BATON_PASSWORD: <Password for Confluence Data Center account> # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true
See the connector’s README or run --help to see all available configuration flags and environment variables.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.
That’s it! Your Confluence Data Center connector is now pulling access data into ConductorOne.
