JIRA Server is an issue-tracking product used for project management, generating project reports, and bug tracking.

To configure the connector, following parameters are required:

• Connector name

• Username

• Password

• SCIM URL

Supported objects and operations

Users

Table 25: Supported operations for Users

Operation	VERB
Remove/Provision	POST
Update (Id)	PUT
Delete (Id)	DELETE
Get (Id)	GET
Get All Users	GET
Pagination	GET

Groups

Table 26: Supported operations for Groups

Operation	VERB
Create	POST
Update (Id)	PUT
Delete (Id)	DELETE
Get (Id)	GET
Get All Groups	GET
Get Groups (Id)	GET

Roles

Table 27: Supported operations for Roles

Operation	VERB
Get All Roles	GET
Get Role (Id)	GET

Mandatory fields

Users

• User name
• Display name
• Email ID

Groups

• Group Name

User and Group mapping

The user and group mappings are listed in the tables below.

Table 28: User mapping

SCIM parameter	JIRA Server parameter
Id	name
UserName	name
password	password
Name.Formatted	displayName
DisplayName	displayName
Emails.Value	emailAddress
Locale	locale
Timezone	timeZone
Active	active
Groups.value	group.name
Groups.display	group.name

 

Table 29: Group mapping

SCIM parameter	JIRA Server parameter
Id	name
DisplayName	name
Members.value	user.name
Members.display	user.displayName

Connector limitations

• The following dates are not available in User and Group resources.
  • created
  • lastModified

• Pagination is not supported for Groups.

• Update Group can only be used for membership management.

• Since the application does not support id, the URL encoded user name or group name is assigned as id for the resource.

• Leading slash (/) in clientRequest, in the RequestWrapper is restricted in REST Client (Eg: Postman) testing.

• Invalid host name in target URL returns error 500.

• The connector does not support special characters in the object ID. For more information, see Connectors that do not support special characters in the object ID