SonarCloud PAT Issue – Logout When Updating Azure DevOps Token

SonarQube Cloud
1

Hi Team,

We are experiencing a recurring issue with SonarCloud authentication related to Azure DevOps integration.

When the Personal Access Token (PAT) expires, all our Pull Requests fail in the pipeline. To resolve this, we generate a new PAT in Azure DevOps and update it in SonarCloud. However, immediately after updating the new token in SonarCloud, we are automatically logged out of SonarCloud.

After logging back in, the issue still persists or the token becomes invalid again after some time.

This behavior is impacting all our active PRs and blocking code merges, affecting our development and release timelines.

Could you please help us understand:

  • Why updating the Azure DevOps PAT in SonarCloud logs us out

  • Why the PAT keeps becoming invalid at regular intervals

  • Whether this is an organization-level configuration issue

  • The recommended best practice to avoid repeated token failures

This is currently a critical blocker for our team. We would appreciate your urgent guidance.

Thanks in advance.

2

Hi @Gokulakrishnan may be worthwhile looking into this - Valid Azure DevOps PAT stops working after a few weeks - #3 by Leuko

3

Dear Erica,

image
image1603×105 5.46 KB

There is no issue with PAT

As mentioned earlier, the token becomes invalid after a few days of use. When we attempt to update the token, Sonar Cloud automatically logs us out.

4

Hello,
We are experiencing similar issues with an invalid PAT. Unfortunately, we are unable to edit the token, as attempting to open the organization binding results in us being logged out .

5

Hello @Gokulakrishnan & @m.katzenschlager,

We’ve just deployed a fix that we believe will resolve this issue. Please let me know here if you still see otherwise.

Best, Wayne

6

Dear Wayne khan

Still the same issue exists.

7

Also getting the same issue, getting logged when trying to update the PAT in Organization Bindings

8

Unfortunatelly, still the same issue.
BR Michael

10

Hey everyone,

We have identified the issue and are deploying a fix right now.

We will get back to you once it’s stable again.

Sorry for the inconvenience!

11

The issue should be fully resolved now!

Please let us know if you encounter any further problems.

12

Dear Julien,

The issue is resolved.

3 Likes