Hi Rakesh,

Yes, R&D is already working on this.

It's taken us all by surprise - including our Jira Cloud customer base...

I understand it has affected other (non MicroFocus) products as well.

In the interim, you may want to contact Jira Cloud Support directly.

Cite case.... JST-843586 

https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-843586

Atlassian are investigating a workaround wherein they can offer a small set (1 or 2) of service accounts which bypass the long (512 char) api key rule.

You will need to provide them with the url to your atlassian instance as well as the email address of the service account.

imo, it seems odd they did this without putting the exceptions in place up front, but there you have it.

take care

anil

Thank you Anil . Appreciate the quick response

You are very welcome.

Incidentally, if you're on the vanilla (4.4.3 release) that went out to marketplace a year ago, I'd recommend upgrading to the latest set of hotfix connectors which were released in january.

please send an email to dl-connect-cfrd@microfocus.com

we'll be glad to send you instructions.

Please also raise a support incident, reference this post, so we can track  & notify you when the fix actually comes out.

Hi Rakesh, R&D have suggested that you can also email us dl-connect-cfrd@microfocus.com with your Jira cloud URL and the datasource (service account) email, we will reach out to Atlassian  and get your service account email to bypass the 512 character rule. (down to 112 characters). I understand that it's a 90 day temporary workaround, and their turnaround is pretty fast. 48 hours or so. 

I am not able to email this DL  . The email bounced , looks like it foes not accept an email from outside of microfocus. Is there another way i can communicate the information you requested

Our licensing for Microfocus products is through our SAP contract . So i have raised a ticket in SAP portal

Anil Hi!!, we have some solution about this issue??? thanks!!!

Do you have any info to share, thanks!

Hi Karen,

I'm afraid we do not have a solution yet.

Our workaround continues to be - notify us, we'll get a temporary exception from Atlassian

Hello Anil,

Any updates on this issue.  From talking to Atlassian we understand that the short api key exception is a temporary workaround.  Is there an ETA for MF Connect being able to handle the 512 char key required by Jira?

Thank You,

Sergio Rojas