I have been using these APIs for a while, but suddenly we noticed that they started throwing 401 on direct logins. This worked with HTTP Auth 2020-07-08, so it’s a recent change.
What seems to have changed is, that I’m no longer able to login to id.atlassian.com with password, but it enforces me to login via Google (yep, I got google apps connected).
What is the suggested way forward here? I want to have a limited read-only api user for reporting purposes, but it seems I can’t create one in the marketplace and I’m not really sure now where to create it. Preferred solution would of course be to have only an API Key for this, but that seems to not be available for the marketplace.
Looking forward to an answer to this as well, since we rely on the Marketplace API. Hopefully, we can avoid having to create an artificial user to work around this.
Apologies for the delay in responding to this thread. I opened a public facing bug with a workaround. Please have a look : [AMKT-23472] - Ecosystem Jira
It would be nice if one could use API Tokens for the Marketplace APIs as well.
That would make it so much easier to manage accounts and access to the APIs.
I use the API to automatically publish new versions to the Marketplace, but now have to create a new account just so I can use basic auth and am not blocked using Google SSO.