Why can I not log in to Jira Cloud from Almworks's Jira Client?

Question

I have been able in the past to log into Jira Cloud from Jira Client for desktop by using a browser.  This feature is no longer available however I cannot refresh my connection directly.   The issue appears to be in the fact that JC is not able to retrieve the account ID. Jira seems to not be accepting the URL brought by /rest/auth/1/session, which is the resource that returns info about the user details.

Is this a bug or is something misconfigured?

Mario O.G · Answer

Hi Randy,

As discussed in our ticket, we are currently working on a patch to address the changes mentioned by Andy.

I will let you know as soon as it becomes available.

Mario O.G
[ALM Works]

PS: Andy, thanks for your support!

Andy Heinzer · Answer

Hi Randy,

I understand that you're using the Jira Client from ALM Works, but that you are unable to use this with Jira Cloud today.  From looking at that page in Marketplace it makes it appear that this is only intended for Jira Server.

I suspect that this is happening because Jira Cloud deprecated the use of passwords/cookie based authentication last year.  More details on that in Deprecation notice - Basic authentication with passwords and cookie-based authentication.  I'm betting that this client was relying upon one of these methods that is no longer available in our Cloud offerings. I should note that I'm not an expert on this vendor's client.  However the way you describe this problem makes it very much sound like this deprecation notice is the cause of the change here.

It might help to reach out directly to ALM Works support through their vendor support link.  No guarantees they can fix this problem, but if you explain your desire to use this with Cloud perhaps they can at least track such requests for compatibility with Atlassian's Jira Cloud.

Atlassian Cloud still does support the use of basic auth for REST, however you need to create an API token and that token has to be passed to Jira Cloud in a specific way in order for REST calls to be authenticated properly.  You cannot simply use the token as a clear-text password today.  That might have worked on previous versions, but today you need to encode youremailaddress:APItoken into a base64 string and then pass that within an authorization header.  Steps to do that are in Basic auth for REST APIs . I'm guessing that this client is not configured to be able to do that today.

I hope this helps.

Andy