Hello - You need a native Jira account to act as the service account for Connect.  You can't use an SSO account in your data source as that authentication won't work over the Jira API. Also, if your Jira instance is Cloud, you need an API token in place of the password. Hope that helps!  

Hi Kelly, 

thanks for the info. 

Yes, Im very aware of your above statement. However, I have same error message with API. 

Update: I got updated info about Jira instance that Im using in my enterprise is a Cloud based Jira but does not go through SSO authentication. 

I also imported SSL certificate. 

Okay, can you confirm these things for me?  

1. For Jira Data Source, URL is just set to: yourinstancename.atlassian.net  with no additional characters after

2. You are using your email address for the username field on the Data Source (since its Jira cloud)

3. When you open a normal browser from that Connect server and go to the highlighted URL above, do you get a Jira login or your company login?

Thanks,

kg

Please see below update.

1) Yes, no space after "t" of .net

2) Yes, Im using email address of the user in Jira Datasource

User that im using in Jira Datasource has as its required permission in Jira. Example: can create any issue type in Jira.

3) I get Jira Login if I have previously launched browser with SSO active session. But, if I launch Jira url in a new or fresh Incognito page, the page 1st lands in Company SSO page and after authentication of SSO, the page lands into Jira login screen. 

Yes, this is where is the confusion and issue. 

I stand by saying Jira is SSO enabled. and you may say the same But, the person who supports Jira instance in my Company says Jira is cloud and Not SSO enabled. that's where i wrote as "update" in my above comment even though originally I posted my Jira is SSO enabled. May be I have to debate internally?

Yes, unfortunately that is where the problem lies.  Your Jira credentials are being routed through your company.  Maybe its not SSO, but some other type of authentication, but whatever it is, its not going directly to Jira which is where Connect is trying to authenticate directly.  Based on your statement, it almost sounds like your colleague thinks that because its Cloud it can't use some other authentication method?

Also, I just tested in Incognito browser as below. 

Im in fresh incognito browser and typed in "gmail" and hit enter. The page routes to company SSO page and asked me to enter SOS credentials.  

Okay, so might be based on your machine login, or browser settings, etc.  Either way, I think you've found the problem.

Jira Admin in my company creates user's account with company email address and let user setup his/her own password and user full name. So, Jira Admin says, Jira let you login with the company email address and its manual password and also you can launch company's Jira url from any network not necessarily from company network. I can be on my home network and use my personal PC to access my company Jira url which will only go Jira login screen but not Company SSO login page.

Jira Admin in my company creates user's account with company email address and let user setup his/her own password and user full name. So, Jira Admin says, Jira let you login with the company email address and its manual password and also you can launch company's Jira url from any network not necessarily from company network. I can be on my home network and use my personal PC to access my company Jira url which will only go Jira login screen but not Company SSO login page.

Using OAuth perhaps?

Sorry, did get it about OAuth.

They might be using OAuth or some other authentication option in Jira (not basic with token) that takes it through an additional authorization step.  Either way, Connect requires Basic Jira Authentication (with an api token for Cloud.)

Sounds like its dead end here.

Just curious, does MF Connect team has any success stories in similar scenarios? How have customer/s accomplished in similar situation? 

Every team I've worked with using other authentication mechanisms (like OAuth) was able to create a service account for Jira using Basic Authentication and API token. So its never been a dead end so far, but has required extra steps in those cases. 

Im not sure if my company Jira instance is using OAuth or something. but, the user/service account that is created for ALM-Jira and Octane-Jira sync has basic authentication and also has API token. Both failed to create jira data source. 

I have case opened for it and have not seen progress even though Support person has devoted his time on it. 

You have helped me a lot in past. 

May be I will email you so, we can connect offline and once we finalize the issue I or you can post the success story here?

Hi

>>I have case opened for it and have not seen progress even though Support person has devoted his time on it

What is the case number please?

Thank you

Thanks Anil looking at it. 

Email sent to you with the case #.

The selected username MUST have the ‘Administrators’- role for the Jira Roles in the selected Project.