After doing an upgrade from 1.0 to 1.1, following the upgrade instructions, I get the following message when hitting the main page:

Incorrect username or password.

This is being rendered to the browser as plain text, not HTML.

Thinking it may be a cookie pointing to a stale session, I removed all cookies from that domain, and also restarted the browser, but the problem still persisted.

This is in the production.log (with any private data scrubbed):

Processing ProjectsController#index (for xx.xxx.x.xx at 2007-10-31 23:13:38) [GET] Session ID: 8ce6047d89a2d767a4c8bdf46b3a3f49 Parameters: {“action”=>”index”, “controller”=>”projects”}
Filter chain halted as [#<actioncontroller::filters::classmethods::symbolfilter:0x4daaf194>] returned false.
Completed in 0.11900 (8 reqs/sec) | Rendering: 0.00000 (0%) | DB: 0.00000 (0%) | 401 Unauthorized [http://mingle.xxxxxxxx.com/]

I was able to rollback to the 1.0 release from backups.

I am not using ldap and, and no auth_config.yml file existed in the mingle data dir, fwiw.

Hi Ken -

auth_config.yml is not required to run Mingle. you will get all default settings without that file.

i’m not sure what could be causing this trouble. any chance you could try a clean install of 1.1 and see if you get the same trouble?

David,

A brand new install against a different db/data dir w/o our project in it seems to go through ok. It’s when I point it to our current 1.0 data dir and db that I get that problem.

Just did the whole upgrade to 1.1 against a freshly-untarred mingle 1.1 again, with a fesh backup of our 1.0 db ad data and got the same result. “Incorrect username or password.”

This issue has been resolved in the just released Bug Fix Release mentioned here: http://studios.thoughtworks.com/discussion/forums/2/topics/359