Confluence connection
Confluence is a content collaboration tool that helps teams to create, share and manage content in a centralized repository.
Supported versions
Confluence 10.1
Prerequisite
Before you can connect to Confluence connection, you need to enable the AppConnect connection. This will enable the connection to appear in the list of available connectors for you to use.
Enabling IBM Confluence connector
To enable the connector, you need to run the following:
- Login to the cluster and enable AppConnect:
Then in theoc login -u <username> -p <password> <host:port> oc project cpd oc edit datasift datasift-crspecsection:set enableAppConnect: true - Login to the cluster and edit the configmap
auto-register-custom-datasource-typeswith the following details:
Then in theoc login -u <username> -p <password> <host:port> oc project cpd oc edit cm config-wdp-connect-connectiondatasection:Alternatively, you can manually register by running:set auto-register-custom-datasource-types: appconnect_confluence:grpc+tls://wdp-connect-adapter-appconnect:443curl --request POST \ --url '<API_HOST>/v2/datasource_types' \ --header 'Authorization: Bearer <TOKEN>' \ --header 'Content-Type: application/json' \ --data '{ "flight_info": { "flight_uri": "grpc+tls://wdp-connect-adapter-appconnect:443", "ssl_certificate_validation": "false" }, "origin_country": "us" }'
Create a connection to Confluence
To create the connection asset, you need these connection details:
- Endpoint URL: The URL for the Confluence server.
- Authentication type: Choose the type of authentication you want to use. The options are:
- BASIC
Credentials
- User name: The user name for the Confluence account you want to use.
- Password or API token: The password used for your Confluence on-premises account, or the API token used for your Confluence cloud account.
- Rest API URI: This field is only required if you are connecting to an on-premises Confluence instance. You will need to specify the API URI based on if you are deploying with a context or without a context.
- API URI with context:
/<context-name>/rest/api - API URI without context:
/rest/api
- API URI with context:
For Credentials and Certificates, you can use secrets if a vault is configured for the platform and the service supports vaults. For information, see Using secrets from vaults in connections.
Federal Information Processing Standards (FIPS) compliance
This connection cannot be created in a FIPS environment.