Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Summary

After applying the API access token on the Salesforce package an "Unauthorized Endpoint" message appears and the page is stuck in a loop:

Another error that can be seen after adding the API token:

Environment

  • Jira Cloud or Jira Server

Cause

EnvironmentCause
CloudThis is usually caused by the Connector's server URL not being configured in 'Remote Site Settings'.
ServerThis is usually caused by the Jira instance URL not being configured in 'Remote Site Settings'.

...

EnvironmentResolution
Cloud
  1. Go to the Salesforce page. In the Quick Find box in the sidebar, type "remote site settings".
    Image Modified
  2. Click the Remote Site Settings link that appears.

  3. On the All Remote Sites screen, click the New Remote Site button.
    Image Modified

  4. On the Edit Remote Sites screen, enter the following details:
    Remote Site Name:  Jira
    Remote Site URL:  https://sfjc.servicerocket.io/
    Image Modified

  5. Click Save.
  6. Please revoke the access from both ends

  7. Re-authorize the connection 

  8. Copy a new API Token from the Connector configuration in JIRA

Server
  1. Go to the Salesforce page. In the Quick Find box in the sidebar, type "remote site settings".
    Image Modified
  2. Click the Remote Site Settings link that appears.

  3. On the All Remote Sites screen, click the New Remote Site button.
    Image Modified
  4. On the Edit Remote Sites screen, enter the following details:
    Remote Site Name:  Jira
    Remote Site URL:  <enter your Jira instance URL>
    Image Modified

  5. Click Save
  6. Please revoke the access from both ends

  7. Re-authorize the connection 

  8. Copy a new API Token from the Connector configuration in JIRA

If after following all these steps the issue persists, please verify that your Jira instance meets all the system requirements, you can find more information about it here