Atlassian Confluence Connector#
Squirro provides a 1-Click Connector for Confluence. This connector allows the Project Creators to connect to an Atlassian account and index the Confluence data into Squirro.
Setting Up a Connector#
Usage assumes that the OAuth setup for the 1-click connectors has already been done on the server. This is by default available on all of our cloud servers at https://start.squirro.com. For any other Squirro installation, please ask your Squirro server admin to follow the steps in the For any other Squirro installation, follow the steps in the OAuth Configuration section below.
Head over to the Enterprise tab on the Data screen as shown in the screenshot below.
Click on the Confluence icon. Squirro will show a prompt asking you to authenticate your Atlassian account. Click on the Authenticate button there.
Once you click on the Authenticate button, you will be re-directed to the Sign-in screen hosted by Atlassian.
Squirro will never ask you for your Atlassian password. This is requested by Atlassian itself.
Once you sign-in you will be prompted to approve Confluence scopes. This screen is presented to you by Atlassian asking you to provide consent for your Confluence data to Squirro.
After approving scopes and selecting your Atlassian instance (if your account has access to multiple Atlassian instances), you will be brought back to Squirro’s source configuration screen. This screen shows which Atlassian account Squirro has connected to.
Now, you can click Save & Exit for Squirro to automatically configure the mapping of item fields and labels, as well as any other required source configuration.
If your account has access to multiple Atlassian instances, Squirro will index data from the first found instance by default. The searching instance process is not deterministic and the found instance may vary across OAuth authentications. To select specific Atlassian instance provide Atlassian instance URL in the Advanced Options section.
Alternatively you can define those settings manually by clicking Next and going through the whole source setup process. This allows you the full flexibility of how the Confluence data should be mapped to Squirro items.
After clicking on Save & Exit, you will see your source running. Sit back, relax, and enjoy as your Confluence data is indexed into Squirro.
You will need to register an OAuth2 app on the Atlassian portal to allow Squirro to connect to the Atlassian accounts of end users. Please follow the steps below to do so.
Note that the exact process on the Atlassian platform may change. If you notice big discrepancies between the current Atlassian website and the documentation page here, please reach out to Squirro’s support at firstname.lastname@example.org for help.
Go to Atlassian Developer Console here: https://developer.atlassian.com/console/myapps/, click on the Create button and choose OAuth 2.0 (3LO) integration option.
On the next screen, choose the name of your app, accept the terms and click the Create button.
In the Permissions tab add Confluence API service.
After adding Confluence API service, click the Configure button and add the following scopes:
Read Confluence space summary
Read Confluence content properties
Read Confluence detailed content
Read Confluence content summary
Search Confluence content and space summaries
Read user groups
Download content attachments
Switch to the Authorization tab and configure OAuth 2.0 Authorization by clicking Configure button.
On the next screen configure OAuth 2 Callback URL. This is the URL Atlassian will redirect the user to after successful authorization. This needs to be set to
https://<your-server-url>/dataloader/confluence_plugin/pl/atlassian/authorizedon your server.For example:
https://squirro.example-company.com/dataloader/confluence_plugin/pl/atlassian/authorized.After that click Save changes button.
Apply for Production#
Also note that the apps are listed as a private by default. It means that only the owner of the app may grant it access to their account. The app will also show a warning about Development status during the user authorization process when the users connect their Squirro instance to their Atlassian account. To avoid that, you have to apply for publishing the Confluence app.
After having created the OAuth2 app on the Atlassian portal, you need to configure the Client ID and the Client Secret on your Squirro instance.
Get the Confluence Client ID and the Client Secret from the Settings tab of the app.
This configuration will soon be possible from the user interface.
/etc/squirro/common.inion your Squirro cluster and add the following lines:
confluence_client_id = YOUR_ID
confluence_client_secret = YOUR_SECRET
[dataloader]header is already present in this file, add the two lines to the existing section. The section header can not appear more than once in the configuration file.
Restart the frontend & datasource service to apply the settings:
sudo systemctl restart sqfrontendd
sudo systemctl restart sqdatasourced
Confluence / Jira GPDR Compliance#
Atlassian imposes rules on the handling of user personal data to be compliant with GDPR regulations for apps building on top of Atlassian products:
Squirro’s 1-Click Connector does not store any personal data of any Atlassian user. It uses OAuth for Authorization. The process does not disclose any personal information, neither does Squirro store user personal data generated / stored in an Atlassian product in Squirro.