Overview Atlassian Cloud Connector
The IDHub Atlassian Cloud connector manages user accounts, groups, Jira project roles and Confluence spaces.
For more information about the Connector Health and it's status, Click here
Architecture
The connector's architecture is constructed in accordance with the diagram below: The connector architecture primarily consists of a connector application and a target system component. This architecture is implemented because it allows for rapid and straightforward connector deployment as well as precise versioning capabilities.
Features
- Account Management for Users
- Account - Group Management
- Entitlement Management - Jira Project Roles
- Entitlement Management - Confluence Spaces
- Authentication Features
- OAuth 2.0 Authentications
- Multi-factor Authentication(MFA) Management
- Single Sign On (SSO) Management
Below are the features in details.
Account Management for Users
This section describes the supported features of Atlassian Connector for Users management:
All users created, modified and deleted will be done using identity provider and specific directory in Atlassian.
| Operation | Supported |
|---|---|
| Create user | Yes |
| Update user | Yes |
| Enable/Disable user | Yes |
| Fetch Account | Yes |
| Account Reconciliation | Yes |
| Add/Remove Entitlements Add/Remove Jira Project Roles Add/Remove Confluence Spaces Add/Remove Groups | Yes |
Account - Group Management
IDHub Atlassian connector connector pulls all Atlassian Groups and keep them in IDHub as Entitlement type ‘Group’. Groups are used to provide permissions to various applications in Atlassian. You would need to define the default group (in case more than one default groups are present) for Jira and Confluence product provisioning.
Entitlement Management - Jira Project Roles
Jira Project Roles are valued entitlements of Atlassian. It provides access to particular permission within Jira software in Atlassian. The Atlassian connector pulls are project information from your Atlassian instance and roles present in each project. No additional service account permission is needed that the Org admin and Site admin.
Following features are supported for Atlassian Jira Project.
| Operation | Supported |
|---|---|
| Fetch Projects and Project Roles | Yes |
| Reconcile Members to Project Roles | Yes |
| Add/Remove Member to Project Roles | Yes |
Some common project roles that Jira software has are ‘Sevice Desk Team Member’, ‘Administrator’, ‘Member’, Viewer' etc.
Entitlement Management - Confluence Spaces
Confluence Spaces are valued entitlements as well for Atlassian. It provides access to particular permission within Confluence Product in Atlassian. The Atlassian connector pulls all confluence spaces information from your Atlassian instance. No additional service account permission is needed that the Org admin and Site admin.
Following features are supported for Atlassian Confluence spaces.
| Operation | Supported |
|---|---|
| Fetch Spaces and Space Permissions | Yes |
| Reconcile Members to Space Permissions | Yes |
| Add/Remove Member to Space Permissions | Yes |
We do not support adding groups and anonymous permissions to spaces currently. Only user management of spaces are done in IDHub.
Authentication Features
IDHub uses Keycloak to use its Authentication features. SAML based Single Sign-On and MFA Setup can be done with your Atlassian instance outside of Connector features.