Issue with OAuth Authentication for Incoming Mail Server – XSRF Security Token Missing & Access Toke

[Christophe Favoreel]

Hi

We are using Jira Cloud with an incoming mail server (Microsoft 365) to automatically create support tickets from emails. Since yesterday, this functionality is no longer working correctly. When we try to re-authenticate the incoming mail server via OAuth, we see:

• In the UI: a message that authentication was successful.
• But in the logs, we keep getting this error:

  RATE_LIMITED
  Retrying in 640 minutes - Email pulling has failed 11 times consecutively
  Reason: Could not retrieve access token for connection [4]

Additionally, when saving the configuration, we frequently encounter this error:

XSRF Security Token Missing
Your browser has not provided any parameters at all and your input has been lost.
Request URL: /secure/admin/IncomingMailServers!saveConfig.jspa

It seems Jira does not persist the new OAuth configuration, so the old (invalid) token remains active.

---

What we have already checked / done:

• Microsoft Entra (Azure AD) configuration:
  • Jira Cloud app has the correct permissions: Mail.ReadWrite, offline_access, User.Read, openid.
  • Admin consent has been granted for all permissions.
• Mailbox we use to authenticate:
  • Active, no MFA, no Conditional Access applied.
• Browsers tested: Chrome, Edge, private/incognito mode, cleared cookies.
• No recent changes in Jira configuration (except re-authentication).
• Network access: Jira can reach Microsoft Graph endpoints.

Impact:

• Incoming emails are not processed → support tickets are not created.
• Logs are filled with OAuth token errors.

Is there any workaround to bypass the XSRF Security Token Missing error in Jira Cloud?

Thank you in advance for your help.
Christophe

[Philipp Sendek]

Hi @Christophe Favoreel ,

especially due to the urgency I gather from your request, this is something that you should direct to the Atlassian Support. You can create a ticket here: https://getsupport.atlassian.com/

They should be able to help you troubleshoot this properly and also rule out any serverside issues or at least be able to check logs on their end.

Greetings
Philipp

[Christophe Favoreel]

Thank you Philipp, I created a new ticket at https://support.atlassian.com/requests/JST-1241980/