New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect #77

Closed
lostumbrellas opened this Issue May 1, 2017 · 24 comments

Comments

Projects
None yet
6 participants
@lostumbrellas

lostumbrellas commented May 1, 2017

Unable to connect, and getting these errors in the log:

1/05/2017 2:16:33 PM Try to re-authenticate
1/05/2017 2:16:33 PM Request: https://xxxx.atlassian.net/rest/auth/1/session
1/05/2017 2:16:34 PM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}

Running version 2.0.1

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 1, 2017

Owner

Hmmm.... Not to be rude, but it sounds very much like you have entered a wrong username/email or password. Could you try to type both again?

Owner

carstengehling commented May 1, 2017

Hmmm.... Not to be rude, but it sounds very much like you have entered a wrong username/email or password. Could you try to type both again?

@lostumbrellas

This comment has been minimized.

Show comment
Hide comment
@lostumbrellas

lostumbrellas May 1, 2017

Ha, I agree, sounds like that a lot. But sadly no, have triple checked the username and password.

I was wondering whether it was something to do with the introduction of a single Atlassian Accounts for all their products? https://confluence.atlassian.com/cloud/atlassian-account-for-users-873871199.html

lostumbrellas commented May 1, 2017

Ha, I agree, sounds like that a lot. But sadly no, have triple checked the username and password.

I was wondering whether it was something to do with the introduction of a single Atlassian Accounts for all their products? https://confluence.atlassian.com/cloud/atlassian-account-for-users-873871199.html

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 1, 2017

Owner

I haven't heard or read about any changes in this regard when it comes down to the Jira REST API. On a daily basis, I use Jira from a self-hosted installation though, so I wouldn't be the first to experience hiccups like this. I'll try to create a cloud account and test it through.

Owner

carstengehling commented May 1, 2017

I haven't heard or read about any changes in this regard when it comes down to the Jira REST API. On a daily basis, I use Jira from a self-hosted installation though, so I wouldn't be the first to experience hiccups like this. I'll try to create a cloud account and test it through.

@moorereason

This comment has been minimized.

Show comment
Hide comment
@moorereason

moorereason May 3, 2017

I'm seeing similar behavior with JIRA Cloud, but after 30s it connects. Here's the HTTP flow:

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 00s  GET /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 401 Unauthorized

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 00s  GET /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 401 Unauthorized

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 30s  GET /rest/auth/1/session HTTP/1.1
< 30s  HTTP/1.1 200 OK

moorereason commented May 3, 2017

I'm seeing similar behavior with JIRA Cloud, but after 30s it connects. Here's the HTTP flow:

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 00s  GET /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 401 Unauthorized

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 00s  GET /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 401 Unauthorized

> 00s  POST /rest/auth/1/session HTTP/1.1
< 00s  HTTP/1.1 500 Internal Server Error

> 30s  GET /rest/auth/1/session HTTP/1.1
< 30s  HTTP/1.1 200 OK
@cpjolly

This comment has been minimized.

Show comment
Hide comment
@cpjolly

cpjolly May 16, 2017

We are also seeing the same issue from all our accounts for our Jira cloud instance. Have Atlassian perhaps changed the authentication requirements ?

5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:05 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:05 AM Try to re-authenticate
5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:06 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["You are not authenticated. Authentication required to perform this operation."],"
5/16/2017 9:09:06 AM Try to re-authenticate
5/16/2017 9:09:06 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:08 AM Response: Unauthorized - {"errorMessages":["You are not authenticated. Authentication required to perform this operation."],"
5/16/2017 9:09:08 AM Try to re-authenticate
5/16/2017 9:09:08 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:08 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}

cpjolly commented May 16, 2017

We are also seeing the same issue from all our accounts for our Jira cloud instance. Have Atlassian perhaps changed the authentication requirements ?

5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:05 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:05 AM Try to re-authenticate
5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:05 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:06 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["You are not authenticated. Authentication required to perform this operation."],"
5/16/2017 9:09:06 AM Try to re-authenticate
5/16/2017 9:09:06 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:06 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}
5/16/2017 9:09:08 AM Response: Unauthorized - {"errorMessages":["You are not authenticated. Authentication required to perform this operation."],"
5/16/2017 9:09:08 AM Try to re-authenticate
5/16/2017 9:09:08 AM Request: https://our-account.atlassian.net/rest/auth/1/session
5/16/2017 9:09:08 AM Response: Unauthorized - {"errorMessages":["Login failed"],"errors":{}}

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 16, 2017

Owner

Sounds serious. I will look at this as soon as I can. In the meantime: If there are any developers using StopWatch, who has experienced this, please help me look into it, as my time is very limited at the moment. Just fetch the code and do a step-by-step trace through the JiraClient part. In addition run Fiddler at the same time to see the actual communication happening.

Owner

carstengehling commented May 16, 2017

Sounds serious. I will look at this as soon as I can. In the meantime: If there are any developers using StopWatch, who has experienced this, please help me look into it, as my time is very limited at the moment. Just fetch the code and do a step-by-step trace through the JiraClient part. In addition run Fiddler at the same time to see the actual communication happening.

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 16, 2017

Owner

I have just tried to make a test Jira cloud site at Atlassian. And I can connect without any problems. Could you please try with the same test-site in your installed Jira StopWatch:

Base URL: https://testgehling2.atlassian.net
Username: carsten@gehling.dk
Password: Simple3ACL

Let me know it it works or not.

UPDATE: I've now closed the site above again, since it was only an 8-day trial.

Owner

carstengehling commented May 16, 2017

I have just tried to make a test Jira cloud site at Atlassian. And I can connect without any problems. Could you please try with the same test-site in your installed Jira StopWatch:

Base URL: https://testgehling2.atlassian.net
Username: carsten@gehling.dk
Password: Simple3ACL

Let me know it it works or not.

UPDATE: I've now closed the site above again, since it was only an 8-day trial.

@cpjolly

This comment has been minimized.

Show comment
Hide comment
@cpjolly

cpjolly May 17, 2017

Hi Carsten,

Yes that works !!

My credentials still fail... I will try to create a test account with our Atlassian instance and see if that works.

cpjolly commented May 17, 2017

Hi Carsten,

Yes that works !!

My credentials still fail... I will try to create a test account with our Atlassian instance and see if that works.

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 17, 2017

Owner

@lostumbrellas @moorereason could you both try the same please?

Owner

carstengehling commented May 17, 2017

@lostumbrellas @moorereason could you both try the same please?

@moorereason

This comment has been minimized.

Show comment
Hide comment
@moorereason

moorereason May 17, 2017

It's all working fine today (with my own account and the test account above). I'm guessing Atlassian fixed something. ?

moorereason commented May 17, 2017

It's all working fine today (with my own account and the test account above). I'm guessing Atlassian fixed something. ?

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 17, 2017

Owner

Yeah - based on your HTTP flow, it seems that they've got some temporal glitches. I'm glad that's all this was. Closing this issue.

Owner

carstengehling commented May 17, 2017

Yeah - based on your HTTP flow, it seems that they've got some temporal glitches. I'm glad that's all this was. Closing this issue.

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 17, 2017

Owner

@cpjolly please let me know about your experience with a new account.

Owner

carstengehling commented May 17, 2017

@cpjolly please let me know about your experience with a new account.

@cpjolly

This comment has been minimized.

Show comment
Hide comment
@cpjolly

cpjolly May 18, 2017

No matter what I tried, it doesn't work with our credentials and our Jira Cloud instance.

I've logged an issue with Atlassian because I think this is due to the problems they have been having with the Atlassian id SSO service and may not be directly related to Stop Watch

cpjolly commented May 18, 2017

No matter what I tried, it doesn't work with our credentials and our Jira Cloud instance.

I've logged an issue with Atlassian because I think this is due to the problems they have been having with the Atlassian id SSO service and may not be directly related to Stop Watch

@ECGroupIT

This comment has been minimized.

Show comment
Hide comment
@ECGroupIT

ECGroupIT May 18, 2017

Hi Carsten,

Further to my earlier email to you I have tried your test instance and it works, so there is some issue with my Atlassian credentials. Also, others in our organisation can connect with StopWatch so it appears to be something to do with my credentials.

I'll raise an issue with Atlassian.

Thanks
Mark

ECGroupIT commented May 18, 2017

Hi Carsten,

Further to my earlier email to you I have tried your test instance and it works, so there is some issue with my Atlassian credentials. Also, others in our organisation can connect with StopWatch so it appears to be something to do with my credentials.

I'll raise an issue with Atlassian.

Thanks
Mark

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 18, 2017

Owner

@cpjolly:

I've logged an issue with Atlassian because I think this is due to the problems they have been having with the Atlassian id SSO service and may not be directly related to Stop Watch

I haven't heard about this - do you have any further info about it? A link to something from Atlassian perhaps?

Owner

carstengehling commented May 18, 2017

@cpjolly:

I've logged an issue with Atlassian because I think this is due to the problems they have been having with the Atlassian id SSO service and may not be directly related to Stop Watch

I haven't heard about this - do you have any further info about it? A link to something from Atlassian perhaps?

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 18, 2017

Owner

@mark: Thank you for your input. As @cpjolly states, the problems probably originates within Atlassian. But I still would like to make sure that Jira StopWatch is lenient in regard to stuff like this. So I'll see if something can be changed in the components that communicate with the Jira API.

Owner

carstengehling commented May 18, 2017

@mark: Thank you for your input. As @cpjolly states, the problems probably originates within Atlassian. But I still would like to make sure that Jira StopWatch is lenient in regard to stuff like this. So I'll see if something can be changed in the components that communicate with the Jira API.

@lostumbrellas

This comment has been minimized.

Show comment
Hide comment
@lostumbrellas

lostumbrellas May 18, 2017

@carstengehling I know you've closed your test cloud account, but here's something I think is relevant. If I go to your login page (https://testgehling2.atlassian.net/login) the username/password form appears. If I go to to the equivalent URL for my cloud account (https://myaccount.atlassian.net/login) I'm redirected to https://id.atlassian.com/login. Atlassian has been gradually migrating accounts over to the Atlassian ID, so I'm wondering if there is something different in the authentication process for those accounts?

lostumbrellas commented May 18, 2017

@carstengehling I know you've closed your test cloud account, but here's something I think is relevant. If I go to your login page (https://testgehling2.atlassian.net/login) the username/password form appears. If I go to to the equivalent URL for my cloud account (https://myaccount.atlassian.net/login) I'm redirected to https://id.atlassian.com/login. Atlassian has been gradually migrating accounts over to the Atlassian ID, so I'm wondering if there is something different in the authentication process for those accounts?

@lostumbrellas

This comment has been minimized.

Show comment
Hide comment
@lostumbrellas

lostumbrellas commented May 18, 2017

Looks like there is a problem with the API: https://jira.atlassian.com/browse/JRACLOUD-66793

@cpjolly

This comment has been minimized.

Show comment
Hide comment
@cpjolly

cpjolly May 19, 2017

Yep - that fixed it !!!!!!!!!!!!!

  • Login to Jira
  • go to profile
  • see what your username name is
  • use that rather than email address

This is part of the roll-out of Atlassian id and SSO. The problem is Atlassian don't tell you when they've changed your Jira cloud instance - the first you know is when connections like this fail.

cpjolly commented May 19, 2017

Yep - that fixed it !!!!!!!!!!!!!

  • Login to Jira
  • go to profile
  • see what your username name is
  • use that rather than email address

This is part of the roll-out of Atlassian id and SSO. The problem is Atlassian don't tell you when they've changed your Jira cloud instance - the first you know is when connections like this fail.

@ECGroupIT

This comment has been minimized.

Show comment
Hide comment
@ECGroupIT

ECGroupIT May 19, 2017

Thank you @lostumbrellas & @cpjolly, that's fixed it for me as well!

ECGroupIT commented May 19, 2017

Thank you @lostumbrellas & @cpjolly, that's fixed it for me as well!

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 19, 2017

Owner

Well done guys, thank you very much! I will update the documentation to include this.

Owner

carstengehling commented May 19, 2017

Well done guys, thank you very much! I will update the documentation to include this.

@carstengehling

This comment has been minimized.

Show comment
Hide comment
@carstengehling

carstengehling May 19, 2017

Owner

Documentation now updated - again thank you all for discovering this.

http://jirastopwatch.com/doc/

Owner

carstengehling commented May 19, 2017

Documentation now updated - again thank you all for discovering this.

http://jirastopwatch.com/doc/

@rdewolfe

This comment has been minimized.

Show comment
Hide comment
@rdewolfe

rdewolfe May 9, 2018

I'm getting a similar error, has anybody gotten this to work using API Tokens?

rdewolfe commented May 9, 2018

I'm getting a similar error, has anybody gotten this to work using API Tokens?

@ECGroupIT

This comment has been minimized.

Show comment
Hide comment
@ECGroupIT

ECGroupIT May 16, 2018

Hi Carsten,

Just to let you know that I continue to have issues with JiraStopwatch logins which require me to reset my password on a daily basis. As I mentioned in one of my earlier posts other users of the tool in my company do not experience this, so it looks like it is something to do with my login. I believe the issue may be related to my login being the site administrator as this is the only difference I can see between it and the other user logins that are working.

In any event, my question to you is, are you planning on implementing Jira API Tokens for this tool? It seems to me that implementing this may resolve this issue once and for all.

Regards,
Mark

ECGroupIT commented May 16, 2018

Hi Carsten,

Just to let you know that I continue to have issues with JiraStopwatch logins which require me to reset my password on a daily basis. As I mentioned in one of my earlier posts other users of the tool in my company do not experience this, so it looks like it is something to do with my login. I believe the issue may be related to my login being the site administrator as this is the only difference I can see between it and the other user logins that are working.

In any event, my question to you is, are you planning on implementing Jira API Tokens for this tool? It seems to me that implementing this may resolve this issue once and for all.

Regards,
Mark

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment