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.
It is never about setting up a process and being done with it. Rather, the focus should always be on optimizing it for the best outcomes. Thus, we didn’t stop at setting up JSM for our recruitment pr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events