Background

Some Jira cloud API functionality is not accessible to cloud apps, such as the ability to lookup user's by their email address (AC-1014). To workaround this limitation, JEMHC requires a preexisting Jira user with appropriate permissions to be configured as a "workaround" user, JEMHC authenticates as this user to perform user lookup API requests that cannot be executed by the JEMHC app user.

Allocating the Global BROWSE_USER permission

Navigate to System > Security > Global Permissions, at the bottom of the screen there is a section to Grant Permission, pick the Browse users and groups, and nominate a restricted membership group, that your workaround user will be a member of:

How to Generate an API Token

Heads up, API tokens last a year and then expire, you will need to redo this every year.

• Login to https://id.atlassian.com/manage/api-tokens

• Click API Tokens

• Click Create API Token

• A dialogue window will appear, enter a descriptive name for the API token in the Label field

• Click Create

• An API Token will be generated and will then appear, press Copy to clipboard to copy the token

How to Configure the JEMHC Workaround User With an API Token

• Browse to the Workarounds tab within JEMHC configuration

• In the E-Mail/Username field, enter the email address or username of the user that was used to generate an API token in the previous part of this tutorial

• In the API Token field, enter the API token generated in the previous part of this tutorial

• Press the Save button