I've already read the article: https://community.atlassian.com/t5/JIRA-questions/REST-SSO-Atlassian-Account-JIRA/qaq-p/580736
With the curl command, we cannot set a password because we authenticate to our JIRA instance and our Atlassian accounts through Azure AD.
We've tried "changing password" in the Atlassian account site but it is unsuccessful because our current password isn't set there and is done through Azure AD.
For the pages I have read, like this one: https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-oauth-authentication/; application links are setup. However, with the current documentation I am unsure what needs to be entered into the Service Provider Name, Consumer Key and Shared Secret fields etc...
This feels like it's not the correct solution as all I should need for OAuth is a token and a secret key for authentication. Can anyone assist me with this?
Please follow below steps to set a password for your user account in id.atlassian.com:
1. Go to https://id.atlassian.com/login/resetpassword
2. Enter you email, complete the CAPTCHA and click on Send
3. Once you receive the password reset email, do not click on the button to access, but on the link below that says "reset password".
4. Fill up the new password and you are done.
Also, as regarding the Oauth documentation. As written just below the screenshot:
"doesn’t matter what you enter for the client application details (URL, name, type, etc). This is because we only want to retrieve data from JIRA, therefore we only need to set up a one-way (incoming) link from the client to JIRA."
Therefore you can just enter random values in there (just as shown in the screenshot). What you have to set are the values in the Link applications dialog (point #4).
Finally, in the same documentation page for JIRA Server you also get a sample certificate you can use for testing pourpose and a more practical example is provided. You may want to review that page as well:
Atlassian Cloud Support
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs