You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Trying to move from Basic Auth (which works in our installation) to using a Personal Access Token (PAT) for a pair of Powershell scripts that do both a GET and a POST. The GET used with the PAT returns a (400) Bad Request while the POST returns a (401) Unauthorized. Both scripts work fine with Basic Auth.
I have seen where the 'Authentication" header duple (name/value pair) needs to look like this for the usage of the PAT ...
Authorization Bearer XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
... where the value is the word Bearer followed by a space and then the full Base64 encoded string displayed with the PAT is created.
Any I missing something in that this method is not working for me? Literally the only change in the code is the value changing from the word Basic followed by the encoded creds to the word Bearer followed by the PAT string.
You probably have solved this by now, but 'Authorization' must be follow by a colon, so:
curl -H 'Authorization: Bearer XXXXXXXXXXXXXXXXX' https://...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.