Atlassian JIRA Confluence
Atlassian JIRA Confluence
Atlassian JIRA Confluence is a connector that links Atlassian software with Jira software. It gives teams the ability to manage projects and track development efforts in the cloud.
NOTE: AtlassianJC supports the Jira software and Confluence
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector Name
-
Username
-
API Key
- SCIM URL (Cloud application's instance URL used as targetURI in payload)
Supported objects and operations
Users
Table 64: Supported operations for Users
Create |
POST |
Delete |
DELETE |
Get All Users |
GET |
Get (Id) |
GET |
Get All Users with pagination |
GET |
Groups
Table 65: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get (Id) |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 66: User mapping
Id |
accountId |
userName |
emailAddress |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
email.value |
emailAddress |
Active |
active |
Timezone |
timeZone |
Locale |
locale |
Groups.Value |
name |
Table 67: Group mapping
Id |
name |
DisplayName |
name |
members.value |
accountId |
members.display |
displayName |
Connector limitations
- Cloud application does not support the Created date and Modified date.
-
Timezone, Active, and Locale are readonly fields.
-
Cloud application does not support the PUT operation for User objects.
-
While trying to create a duplicate user, the cloud application returns an error with the status code 201. But the existing user is retrieved as the result.
-
The Stride application is no longer part of Atlassian.
-
Cloud application does not supports the Get All groups with pagination operation.
-
The cloud application attributes for the cloud API URL is case-sensitive.
Supervisor configuration parameters
Atlassian JIRA Confluence
Atlassian JIRA Confluence is a connector that links Atlassian software with Jira software. It gives teams the ability to manage projects and track development efforts in the cloud.
NOTE: AtlassianJC supports the Jira software and Confluence
To configure the connector, following parameters are required:
-
Connector Name
-
Username
-
API Key
- SCIM URL (Cloud application's instance URL used as targetURI in payload)
Supported objects and operations
Users
Table 64: Supported operations for Users
Create |
POST |
Delete |
DELETE |
Get All Users |
GET |
Get (Id) |
GET |
Get All Users with pagination |
GET |
Groups
Table 65: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get (Id) |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 66: User mapping
Id |
accountId |
userName |
emailAddress |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
email.value |
emailAddress |
Active |
active |
Timezone |
timeZone |
Locale |
locale |
Groups.Value |
name |
Table 67: Group mapping
Id |
name |
DisplayName |
name |
members.value |
accountId |
members.display |
displayName |
Connector limitations
- Cloud application does not support the Created date and Modified date.
-
Timezone, Active, and Locale are readonly fields.
-
Cloud application does not support the PUT operation for User objects.
-
While trying to create a duplicate user, the cloud application returns an error with the status code 201. But the existing user is retrieved as the result.
-
The Stride application is no longer part of Atlassian.
-
Cloud application does not supports the Get All groups with pagination operation.
-
The cloud application attributes for the cloud API URL is case-sensitive.
Supported objects and operations
Atlassian JIRA Confluence
Atlassian JIRA Confluence is a connector that links Atlassian software with Jira software. It gives teams the ability to manage projects and track development efforts in the cloud.
NOTE: AtlassianJC supports the Jira software and Confluence
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector Name
-
Username
-
API Key
- SCIM URL (Cloud application's instance URL used as targetURI in payload)
Users
Table 64: Supported operations for Users
Create |
POST |
Delete |
DELETE |
Get All Users |
GET |
Get (Id) |
GET |
Get All Users with pagination |
GET |
Groups
Table 65: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get (Id) |
GET |
Mandatory fields
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 66: User mapping
Id |
accountId |
userName |
emailAddress |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
email.value |
emailAddress |
Active |
active |
Timezone |
timeZone |
Locale |
locale |
Groups.Value |
name |
Table 67: Group mapping
Id |
name |
DisplayName |
name |
members.value |
accountId |
members.display |
displayName |
Connector limitations
- Cloud application does not support the Created date and Modified date.
-
Timezone, Active, and Locale are readonly fields.
-
Cloud application does not support the PUT operation for User objects.
-
While trying to create a duplicate user, the cloud application returns an error with the status code 201. But the existing user is retrieved as the result.
-
The Stride application is no longer part of Atlassian.
-
Cloud application does not supports the Get All groups with pagination operation.
-
The cloud application attributes for the cloud API URL is case-sensitive.
Mandatory fields
Atlassian JIRA Confluence
Atlassian JIRA Confluence is a connector that links Atlassian software with Jira software. It gives teams the ability to manage projects and track development efforts in the cloud.
NOTE: AtlassianJC supports the Jira software and Confluence
Supervisor configuration parameters
To configure the connector, following parameters are required:
-
Connector Name
-
Username
-
API Key
- SCIM URL (Cloud application's instance URL used as targetURI in payload)
Supported objects and operations
Users
Table 64: Supported operations for Users
Create |
POST |
Delete |
DELETE |
Get All Users |
GET |
Get (Id) |
GET |
Get All Users with pagination |
GET |
Groups
Table 65: Supported operations for Groups
Create |
POST |
Update |
PUT |
Delete |
DELETE |
Get All Groups |
GET |
Get (Id) |
GET |
Users
Groups
User and Group mapping
The user and group mapping is listed in the table below.
Table 66: User mapping
Id |
accountId |
userName |
emailAddress |
password |
password |
Name.Formatted |
displayName |
DisplayName |
displayName |
email.value |
emailAddress |
Active |
active |
Timezone |
timeZone |
Locale |
locale |
Groups.Value |
name |
Table 67: Group mapping
Id |
name |
DisplayName |
name |
members.value |
accountId |
members.display |
displayName |
Connector limitations
- Cloud application does not support the Created date and Modified date.
-
Timezone, Active, and Locale are readonly fields.
-
Cloud application does not support the PUT operation for User objects.
-
While trying to create a duplicate user, the cloud application returns an error with the status code 201. But the existing user is retrieved as the result.
-
The Stride application is no longer part of Atlassian.
-
Cloud application does not supports the Get All groups with pagination operation.
-
The cloud application attributes for the cloud API URL is case-sensitive.