The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

atlassian-operations Terraform provider doesn't work with service accounts — please add scoped-token

Vani Puppireddy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 9, 2026

Hi Atlassian team — writing because we can't use the atlassian/atlassian-operations Terraform provider with a service account, and we'd really like to.

Issue:

Our team uses a service account to manage our JSM Operations setup as code. When we try to run Terraform, we get this error:

"Unable to read user, got an empty response. This could be due to invalid credentials or no user being found for the given email address."

Someone else reported the same error a year ago — see this unanswered thread.

reason:

The provider only accepts classic (unscoped) Atlassian API tokens. It cannot use scoped tokens or OAuth 2.0. But Atlassian only lets service accounts create scoped tokens or OAuth credentials — classic tokens can only be created from a personal Atlassian account. So service accounts are locked out by design.

  • The Teams resource calls https://{domain}.atlassian.net/gateway/api/public/teams/v1/org/. This URL returns 401 for scoped tokens (related: CLOUD-12617).
  • No code in the provider repo uses api.atlassian.com/ex/jira/{cloudId}/..., which is where scoped tokens do work.
  • No OAuth 2.0 support. Verified against the latest release v2.0.3 (March 2026).

Our workarounds:
Fall back to the older opsgenie/opsgenie provider — works with our service account via an Opsgenie API key, but Opsgenie REST APIs shut down on April 5, 2027. Temporary fix only.

Ask:

Please add below atlassian/atlassian-operations:
Scoped-token support via the api.atlassian.com/ex/jira/{cloudId}/... URL pattern.

This would unblock service-account automation before the April 2027 Opsgenie cutoff forces everyone to re-migrate.

Thanks.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Philipp Sendek _catworkx_
Community Champion
June 10, 2026

Hi @Vani Puppireddy and welcome to the community,

this is the Atlassian Community where Atlassian staff, but mostly non-Atlassian-staff are answering community questions.

As you're specifically addressing Atlassian with a feature request / bug, I would recommend you create a support ticket which also mentions the site you're asking for - especially since you're on the Premium plan, you should receive a qualified answer to your request there.

You can create a support ticket here: https://getsupport.atlassian.com/

Greetings
Philipp

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events