AtlassianSDK for .NET C#

Raghavendra Korgal April 25, 2014

Hi,

I am using Atlassian.Jira.dll .NET dll to fetch information about a issue. Using Jira.GetIssue("key") method.

our Jira is integrated with google account.

When i use the following code

var jiraObj = new Jira("https://xxxxx.atlassian.net","username", "password");

Issue issueObj = jiraObj.GetIssue("key1");

While creating Jira instance i am using my google account credentials.

When jiraObj.GetIssue() method is called I am getting " com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password."

Can some one please help me how to fix the above issue.

Regards,

Raghavendra

2 answers

0 votes
Raghavendra Korgal April 26, 2014

Hi Nic,

I followed https://bitbucket.org/farmas/atlassian.net-sdk/wiki/Homelink to download the dll

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 25, 2014

Three possibilities spring to mind

1. You're giving it the wrong username and password

2. You've not got "allow remote access" enabled, although you are trying to get to an OnDemand account, and I think they're always enabled

3. I can't even find "Atlassian Jira .dll", so I can't be sure, but I suspect you're using an incompatible or even bugged version. Where is the documentation you are following for this?

(Also, "key1" is not a valid issue key, so I'm hoping you're just usng key1 as a placeholder)

Raghavendra Korgal April 26, 2014

Hi Nic,

I followed https://bitbucket.org/farmas/atlassian.net-sdk/wiki/Homelink to download the dll

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 26, 2014

Ah, ok, well. that was written for Jira 4.4 and I suspect it is incompatible with later versions.

I'd be tempted to skip it and do the REST calls yourself in your .NET application - it'll be more maintainable as you won't be relying on a 3rd party

Suggest an answer

Log in or Sign up to answer