nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Managed Account Suddenly Cannot Access Using API Token

Angelika Heriyanto

I have one managed account that i used to link between "Jira" and "Gitlab" then suddenly the connection failed and returned me with this error "You currently don't have access to perform this operation."

I have checked and the API Token is still active.

As a comparison I have tried to create a API Token using my own personal account and it worked just fine, looks like the problem is only with this managed account.

Anyone know how to fix this? Any advice is much appreciated! Thank you.

Accepted answers

Marc -Devoteam-

Hi @Angelika Heriyanto

Does the account still have a Jira license or is the managed account disabled?

The don't have access tells me there is something with the account itself.

I would look into that.

All comments

Marc -Devoteam-

Hi @Angelika Heriyanto

Does the account still have a Jira license or is the managed account disabled?

The don't have access tells me there is something with the account itself.

I would look into that.

Angelika Heriyanto

Hi @Marc -Devoteam-

Thanks for responding.

The managed account still have access as follows:
Has access on this site YES
Jira Software NO
Confluence NO
Confluence GUEST NO

and it does have admin rights for the project we want it to manage.

there was no configuration changed done for this managed account.
Last time the api token was working was 8 January 2024. After that all connection failed.

Marc -Devoteam-

Hi @Angelika Heriyanto

Project permissions don't help if the user in question has no license assigned.

No license is "No Access".

Angelika Heriyanto

Hi @Marc -Devoteam-

Thanks for replying me again.

If I understood correctly, you are saying that this "Has access on site" is not sufficient and I need to turn on the one for Jira so that the managed account has access to Jira as well?

Because as mentioned the configuration for this managed account remained the same for 2-3 years, it was just suddenly not working after 8 Jan 2024.

Is there any changes on Jira side that causing this to happens? (if you happen to know)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud