Is there a non-personal API token available for use with Heartbeat?

[Spy]

When migrating from Opsgenie to JSM, setting up Heartbeat discovery requires using an API token for authentication. No configuration similar to Opsgenie's API Key Management was found for this purpose.

Therefore, I would like to ask if JSM provides non-personal API keys or API tokens for configuration.

[Alexander Nilsson]

Hello Spy,

thanks for your question.

The recommended pattern in Jira Service Management  is to use a dedicated technical identity and generate a token for that account (instead of a real person’s user).

• Create a dedicated service account in Atlassian Admin.
• Create an  API Token for that service account (and manage it like a secret: expiry/rotation where possible). 
• Grant only the minimum product access/permissions required for Heartbeat.
  • read:ops-config:jira-service-management
  • write:ops-config:jira-service-management

If you also need a reference for how the token is typically used for REST-style authentication in Atlassian Cloud, see Basic auth for REST APIs.

If this answers your question, please consider accepting the answer so others can find it more easily in the future.

Best regards,
Alex

[Spy]

Hi Alexander,

Thank you for providing such a detailed description.

I really appreciate it, and I’ll try it out soon.

[Jeroen Poismans]

Hi!

Have you tried using the fairly recent Service Accounts?

https://support.atlassian.com/user-management/docs/understand-service-accounts/

[Spy]

Hi Jeroen,

Thank you for your reply.

I haven’t tried it yet because I noticed there’s a limit on the number of service accounts. I’ll try it again later, thanks.