From Setup to Success — All in One Place

Setting up Peeklogic Jira Connector on Salesforce

• Authentication to Jira
• Authentication to Salesforce (PRO)
  1. Connected App to Salesforce
  2. External Client App
  3. Auth.Provider 
  4. Named Credentials to Salesforce

Authentication to Jira

Navigate to Salesforce Setup -> find Named Credentials -> create a New Legacy and select Identity Type:

• Named principal:

1. URL of Jira organization;
2. Username of Jira user (Jira admin);
3. Password:  API token that is generated by this user for Jira Cloud;
4. Jira Password for Jira Server.

Generate API token on Jira site using this link, and use the generated API token instead of password when creating Named Credentials.

• Per user:

Peeklogic Jira Connector allows you to configure integration in a such way that Jira issues created by different Salesforce users will have different reporters in Jira.

Prerequisites:

• Each Salesforce user involved in Salesforce Jira integration should have a corresponding user in Jira;
• Each Salesforce user should be authorized to Jira via Salesforce Named Credentials with the help of Salesforce admin or by themselves;
• Each corresponding Jira user should have enough access rights in Jira to perform Jira issue create, add comment attachment – to mirror capabilities and Jira configuration on Salesforce side.

1. URL of Jira organization;
2. Username of Jira user (Jira admin);
3. API token that is generated by this user;
4. Salesforce admin should share this named credential with profiles of users who will use Jira Connector.

• Every user that will use Jira Connector should create a ‘Authentication Settings for External Systems’ in personal settings in SF:
• Username: username of Jira account;
• Password: API Token that should be generated directly in Jira by every user.

Authentication to Salesforce (PRO)

1. Connected App to Salesforce

• Navigate to Setup -> External Client App Settings -> Create ‘New Connected App’ and configure it.

• Enable OAuth Settings

• For the callback URL set https://example.com/ (we will change it later);
• For Selected OAuth Scopes  please select Full Access(full) and Perform requests at any time (refresh_token, offline_access).

• After saving you need to click on ‘Manage Consumer Details’ and you will see ‘Consumer Key’ and ‘Consumer Secret’, you should copy them.

Notes: It usually takes about 10–20 minutes for the app to start working properly.

2. External Client App (if a connected app is unavailable)

1. Navigate to Setup → App Manager.
2. Click New External Client App.

1. Fill in all required fields: External Client App Name, Contact Email, and Distribution State (leave the default).

1. Make sure to enable OAuth.
2. Set the Callback URL to: https://example.com/ (this will be updated later).
3. Under Selected OAuth Scopes, choose:
4. – Full Access (full)
5. – Perform requests at any time (refresh token, offline access)

6. Enable the Client Credentials Flow

7. All checkboxes in the Security section should be unchecked.

Save the app.

After saving:

1. Click Settings
2. Scroll to OAuth Settings
3. Open Consumer Key and Consumer Secret
4. Copy both values (you’ll need them to create the Auth Provider. Please follow the instructions above on how to create an Auth Provider)

3. Auth.Provider
Create Auth.Provider

• Navigate to Setup->Auth.Provider->create new->select ‘Salesforce’ type and configure it;
• For ‘Consumer Key’ and ‘Consumer Secret’ you should paste from the connected App;
• Paste refresh_token full in Default Scopes.

• Copy Callback URL from Auth.Providers and paste it into the Connected App instead of https://example.com/.

• and paste it into the Connected App instead of https://example.com/.

• or paste in External Client App. Click save.

4. Named Credentials to Salesforce (Named Principal or Per User)

• Navigate to Setup->Named Credentials->create Named Credential and fill in all necessary information where URL – it’s a URL to your Salesforce org (classic version);
• For Authentication Provider select Auth.Provider you created;
• For Scope – paste refresh_token full.

Video of configurations