Collect authentication behavior is complex and confusing

[mitchellsundt]

Migrated to getodk/collect#66 by spacetelescope/github-issues-import

Originally reported on Google Code with ID 552

What steps will reproduce the problem?
1. Set up authenticated access to a server
2. Download a form
3. Change user password
4. Access server again.

What is the expected output? What do you see instead?

One would expect that the change of password would invalidate the authentication set
up with the server, prompting for a new authorization.

In fact, it does nothing, as the connection uses the established credentials.  This
causes failures later on when the app is stopped and restarted.

Very non-transparent.

Reported by mitchellsundt on 2012-04-03 21:56:33