Jira Service Desk Connection

See the Connector Marketplace topic. Please request your administrator to start a trial or subscribe to the Premium Jira Service Desk connector.

Jira Service Desk is Atlassian’s service desk and support ticketing system for IT and customer service teams.

This topic describes how to authenticate to Jira Service Desk and configure any necessary connection properties in the Jira Service Desk connection connector.

Connection Configuration

Each connection property available in the Jira Service Desk connector is explained below.


Connection Name

The name of the connection to be created should be provided. This is the name that will display on the list of available connections.


Auth Scheme

The type of authentication to use when connecting to Jira Service Desk.

Possible Values


URL

The URL to your JIRA Service Desk endpoint.

Example: https://yoursitename.atlassian.net


Cloud Id

The Cloud Id for the Atlassian site that was authorized.

This will be determined automatically during OAuth 2.0 authentication. Do not set a value for Cloud Id when using InitiateOAuth.


Service Desk ID

Service Desk ID of the currently authenticated user.

By default the first Id is returned from an extra call to get all service desks.

You can get the ServiceDeskId by executing a Select query to the ServiceDesks view.


User

The Jira Service Desk user account used to authenticate.


Password

The password used to authenticate the user.


Basic

If Basic is selected, additional configuration parameter will get listed.

API Token

APIToken of the currently authenticated user.


OAuth2

Set this to use OAuth2 authentication.

If OAuth2 is selected, additional configuration parameters will get listed.

Client ID

The client ID assigned when you register your application with an OAuth authorization server.

Client Secret

The client secret assigned when you register your application with an OAuth authorization server.

Refresh Token

The OAuth refresh token for the corresponding OAuth access token.


Enable SSL

Option to enable SSL. This field sets whether the connector will attempt to negotiate TLS/SSL connections to the server. By default, the connector checks the server’s certificate against the system’s trusted certificate store.

SSL Client Certificate

The TLS/SSL client certificate store for SSL Client Authentication (2-way SSL).

The name of the certificate store for the client certificate.

If the store is password protected, specify the password in the SSL Client Cert Password field.

Designations of certificate stores are platform-dependent.

The following are designations of the most common User and Machine certificate stores in Windows:

Certificate DesignationDescription
MYA certificate store holding personal certificates with their associated private keys.
CACertifying authority certificates.
ROOTRoot certificates.
SPCSoftware publisher certificates.

In Java, the certificate store normally is a file containing certificates and optional private keys.

When the certificate store type is PFXFile, this property must be set to the name of the file.

When the type is PFXBlob, the property must be set to the binary contents of a PFX file (for example, PKCS12 certificate store).


SSL Client Cert Type

The type of key store containing the TLS/SSL client certificate.

This property can be set to one of the following values:

Property ValueDescription
USER - defaultFor Windows, this specifies that the certificate store is a certificate store owned by the current user. Note that this store type is not available in Java.
MACHINEFor Windows, this specifies that the certificate store is a machine store. Note that this store type is not available in Java.
PFXFILEThe certificate store is the name of a PFX (PKCS12) file containing certificates.
PFXBLOBThe certificate store is a string (base-64-encoded) representing a certificate store in PFX (PKCS12) format.
JKSFILEThe certificate store is the name of a Java key store (JKS) file containing certificates. Note that this store type is only available in Java.
JKSBLOBThe certificate store is a string (base-64-encoded) representing a certificate store in JKS format. Note that this store type is only available in Java.
PEMKEY_FILEThe certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate.
PEMKEY_BLOBThe certificate store is a string (base64-encoded) that contains a private key and an optional certificate.
PUBLIC_KEY_FILEThe certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate.
PUBLIC_KEY_BLOBThe certificate store is a string (base-64-encoded) that contains a PEM- or DER-encoded public key certificate.
SSHPUBLIC_KEY_FILEThe certificate store is the name of a file that contains an SSH-style public key.
SSHPUBLIC_KEY_BLOBThe certificate store is a string (base-64-encoded) that contains an SSH-style public key.
P7BFILEThe certificate store is the name of a PKCS7 file containing certificates.
PPKFILEThe certificate store is the name of a file that contains a PuTTY Private Key (PPK).
XMLFILEThe certificate store is the name of a file that contains a certificate in XML format.
XMLBLOBThe certificate store is a string that contains a certificate in XML format.

SSL Client Cert Password

If the certificate store is of a type that requires a password, this property is used to specify that password to open the certificate store.


SSL Client Cert Subject

The subject of the TLS/SSL client certificate.

When loading a certificate the subject is used to locate the certificate in the store.

If an exact match is not found, the store is searched for subjects containing the value of the property. If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value “*” picks the first certificate in the certificate store.

The certificate subject is a comma separated list of distinguished name fields and values. For example, “CN=www.server.com, OU=test, C=US, E=support@company.com”.

The common fields and their meanings are shown below.

FieldMeaning
CNCommon Name. This is commonly a host name like www.server.com.
OOrganization
OUOrganizational Unit
LLocality
SState
CCountry
EEmail Address

Upload Keystore File

If SSL is enabled, a keystore file has to be uploaded using this option.


Advanced Configuration

This section contains additional configuration parameters.

Include Custom Fields

Setting to true will cause custom fields to be included in the field listing.


Add Configuration: Additional properties can be added using this option as key-value pairs.


After entering all the details, click on the TEST button.

If the connection service identification and authentication details are provided correctly, a success message stating “connection available” is generated.

Click on the CREATE button to save the changes.

If the details are incorrect or the server is down, you will get a message “Connection unavailable”.

Top