Skip to content
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

401 Unauthorized when creating a new calendar #599

Open
wbloos opened this issue May 26, 2017 · 10 comments
Open

401 Unauthorized when creating a new calendar #599

wbloos opened this issue May 26, 2017 · 10 comments

Comments

@wbloos
Copy link

wbloos commented May 26, 2017

After a routine Lightning upgrade, my Exchange calendar changed to read-only.
I read about issues with "suspend", and followed the suggested solution of removing and re-adding the calendar.
But it seems impossible to re-add the calendar. When choosing to add a new calendar, I keep getting a "401 Unauthorized" upon clicking the button "check server and mailbox".
The server URL is in the form https:///ews/exchange.asmx
I went to the same address in a browser and successfully logged in with my credentials, I am then redirected to the Services.wsdl .
Thunderbird does not ask for credentials. The problem is the same whether I fill in the Active Directory domain or not.

New versions:

  • Thundebird 52.1.1 (64-bit)
  • Lightning 5.4
  • Exchange EWS provider 3.9.0
@wbloos
Copy link
Author

wbloos commented May 26, 2017

Not sure if related to #254

@martok
Copy link

martok commented May 26, 2017

Duplicate of #595, #580 and many others. #580 contains a link to a modifed version 4.0.1003, try that and see if it works - it does for me.

@ds2k5
Copy link

ds2k5 commented Jun 1, 2017

try Username: @yourdomain.tld this worked for me with 4.0.0 Beta 1

https://github.com/ExchangeCalendar/exchangecalendar/releases/tag/v4.0.0-beta1

@wbloos
Copy link
Author

wbloos commented Jun 1, 2017

using username@domain did not work for me, with or without the tld.
the modifed version 4.0.1003 from #580 does work.
thank you for the replies, you made my planing baerable again ;)
However it would be much nicer if there would be an officially supported solution.
Is there a way that we can contribute to that?

@rexberg
Copy link

rexberg commented Jun 8, 2017

I can verify that versions =< 3.9.0 don't work but the 4.0.0-beta1 version works.

@ds2k5
Copy link

ds2k5 commented Jun 8, 2017

@HeadlessChild

Hi, yes in my case this is ture.

@a1xndr
Copy link

a1xndr commented Jun 13, 2017

I was able to get around this by leaving Primary email address blank and using [email protected] as Username. This successfully prompted me for password

@mpashka
Copy link

mpashka commented Jun 20, 2017

I tried latest master and got the same issue.
commit 6116d9c
Merge: e316be3 f53948f
Author: Babu Vincent(bavincen) [email protected]
Date: Wed Aug 3 13:38:48 2016 +0530

After pressing "Check mailbox" button it didn't ask me for the password and in console I see that it is trying to reach my server with domain credentials but without a password.

@floschl
Copy link

floschl commented Mar 27, 2019

I am still having issues related to 401 Unauthorized Access: URL, when trying to create a new calender.
I am on the latest TB60 + 5.0.0-alpha3 version.

If I fill the domain, I cannot get any access at all (401). If I leave it out, I can get temporary access. After a while, the calender gets read-only.
The error console tells me the following:
`POST XHR https://xxx:xxx%@{exchange_server}/ews/exchange.asmx
[HTTP/1.1 401 Unauthorized 20ms]

XML Parsing Error: no root element found
Location: https://xxx:xxx@{exchange_server}/ews/exchange.asmx
Line Number 1, Column 1: exchange.asmx:1:1`

Anybody else is having the same problem with these versions?

@AntriaPan
Copy link

I had the same problem and i have just solve it . The only thing you have to do is enable the setting on you domain (mine is gmail) that is about allow less secure site to have access on your account .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants