I’ve been having an issue ever since the migration to the new scopes mentioned here
It seems to me that when I add more scopes in my OAuth 2 app, I face this issue which is the response from atlassian server. due to the max header size.
To my understanding the access token generated by atlassian after the initial request does contains list of the scopes were requested for, so the more scope I request in my app, cause bigger token size, following bigger request header.
My question what I’m doing here wrong? is this how it supposed to be or do I need to change something?
My OAuth 2 app requires ca. 70 scopes added in order for the user to interact with Our jira cloud space using the API.