456794 - Can no longer authenticate for Weave logins

Status: VERIFIED DUPLICATE of bug 456827

(Cloud Services :: General, defect)

Description

[Al Billings [:abillings - ex-MoCo]]

I've been using Weave for quite a while. A couple of months ago, Chris moved me to the same box as the development team (not sure the name) and I've continued to use it.

As of this morning, I cannot authenticate. This was working yesterday.

Verbose logs say:

2008-09-24 10:32:11	Chrome.Window	INFO	Logging in...
2008-09-24 10:32:11	Chrome.Window	INFO	User string: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1pre) Gecko/20080922020341 Minefield/3.1b1pre
2008-09-24 10:32:11	Chrome.Window	INFO	Weave version: 0.2.6
2008-09-24 10:32:11	Service.Main	DEBUG	Logging in user albill
2008-09-24 10:32:11	Service.Main	DEBUG	Verifying login for user albill
2008-09-24 10:32:11	Service.Main	CONFIG	Using server URL: https://services.mozilla.com/user/albill/
2008-09-24 10:32:11	Service.DAV	DEBUG	checkLogin called for user albill
2008-09-24 10:32:11	Service.DAV	DEBUG	GET request for root folder
2008-09-24 10:32:11	Service.DAV	DEBUG	checkLogin got response status 401
2008-09-24 10:32:11	Service.Util	ERROR	Login verification failed Error code: 401
2008-09-24 10:32:11	Service.Main	INFO	Making sure server is initialized...
2008-09-24 10:32:11	Service.DAV	DEBUG	checkLogin called for user albill
2008-09-24 10:32:11	Service.DAV	DEBUG	GET request for root folder
2008-09-24 10:32:11	Service.DAV	DEBUG	checkLogin got response status 401
2008-09-24 10:32:11	Service.Util	ERROR	Cannot initialize server Error code: 401
2008-09-24 10:32:11	Async.Generator	ERROR	Exception: checkStatus failed
2008-09-24 10:32:11	Async.Generator	DEBUG	Async stack trace:
unknown (async) :: WeaveNotifyWrapper-21 (last self.cb generated at module:wrap.js:93 :: WeaveNotifyWrapper)
module:wrap.js:171 :: WeaveLocalLockWrapper
module:async.js:233 :: AsyncGen_run
module:async.js:332 :: Async_run
module:async.js:352 :: Async_sugar
module:service.js:633 :: WeaveSvc_loginAndInit
chrome://weave/content/login.js:146 :: Login_doOK
chrome://global/content/bindings/dialog.xml:345 :: anonymous
chrome://global/content/bindings/dialog.xml:346 :: _fireButtonEvent
chrome://global/content/bindings/dialog.xml:320 :: _doButtonCommand
chrome://global/content/bindings/dialog.xml:309 :: _handleButtonCommand

Comment 1

[Jesper Hansen]

Please check if your password is still in the Login Manager: Edit => Preferences => Saved Passwords => Not really sure what to look for here. Possibly chrome://Weave

Comment 2

[Al Billings [:abillings - ex-MoCo]]

(In reply to comment #1)
> Please check if your password is still in the Login Manager: Edit =>
> Preferences => Saved Passwords => Not really sure what to look for here.
> Possibly chrome://Weave

You realize that Weave doesn't store its passwords there, right? That's for websites.

In any case, when I tell Weave to log in, it shows the login dialog, which is prepopulated with my account information and passwords (just like always). The server is just refusing to allow many (if not all) accounts to log in.

Comment 3

[Dan Mills [:thunder]]

Weave does store its password and encryption passphrase in the login manager.

However, as you already know by now the problem is that our ldap server is currently down.