Hello!
I need help with the Basic Authentication process of Jira's REST API. With the new updates, the number of characters of the API Key generated by Jira is no longer supported by the password field in Basic Authentication (supports up to 128 characters). Is there a solution that can be implemented to get the integration working again?
I was searching and one of the solutions indicated was that of custom authentication, but the option to create in this format does not appear in the method.
Any tips or suggestions will be greatly appreciated. Thanks in advance!
Hi,
Have you tried this?
I was trying to check the documentation for the Jira API here:
https://developer.atlassian.com/server/jira/platform/rest-apis/
https://developer.atlassian.com/server/jira/platform/basic-authentication/
Regards,
PZ
Hi Caroline,
Can you please provide more details about the API you referenced in this post?
Like the base URL, for instance.
It will be easier for the community to help you if you provide more details.
Hi @Paulo Zacarias ! Thanks for answering.
Of course, the base URL is https://<myenvironment>.atlassian.net. Here is how it's configured right now (the username and password were an email from the company and the old API Key, that was still supported.)
A request example is the following URL: https://<myenvironment>.atlassian.net/rest/api/3/issue/{issueIdOrKey}
Hello! Just to give feedback about this: your solution worked! I used OnBeforeRequest to treat the authentication and with the email and the Atlassian API Key, it started returning all the information.
Thank you so much!
This solution also help me, thanks!
Hey @Agno Silveira / @Caroline Caprini da Silveira I am stuck with this issue as well, can someone help me with clear explanation or snaps on how actually you implemented it. As it is bit confusing for me. Thank you in advance.
My query is listed in this form : https://www.outsystems.com/forums/discussion/104218/jira-rest-api-authentication-using-bearer-token/