Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


AADSTS90015: Requested query string is too long.

Hamilton Beck
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!
Oct 16, 2023

Hello, we leverage JIRA to support our customers as an MSP.
We recently migrated to JIRA cloud from an older server version.

We have recently noticed that when some customers we invite to work with us on projects have SSO enabled within their organization they are unable to accept the invitation email when we set up their user ID. 


They get the following Error Message: 

" AADSTS90015: Requested query string is too long "


I looked at the existing resolutions to this including the decoding of the URL and none of the presented solutions appear to be appliable to our situation. 

Any ideas on what I could do to attempt to resolve this. 

It appears to occur when the customer who is outside our domain either already has their own JIRA instance (internal to their organization, or they have some form of SSO enabled)

Any assistance the community could provide would be greatly appreciated. 


1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 16, 2023

Welcome to the Atlassian Community!

This is what it says it is - your integration is sending a longer string than Jira Cloud has been coded for, so it is failing.  

I think the only fix is to move away from MS, so that you get URLs that are way too long.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events