On Apr 27, 2010, at 7:20 AM, Jeffrey Ollie wrote:
> On Sun, Mar 28, 2010 at 5:36 PM, Benoit Chesneau <
bche...@gmail.com> wrote:
>> On Mon, Mar 29, 2010 at 12:08 AM, Stuart Langridge
>> <
stuart.l...@canonical.com> wrote:
>>> On 03/24/2010 02:33 PM, Jeffrey Ollie wrote:
>>>> I tried updating to CouchDB 0.11, but when I started up my Desktop
>>>> CouchDB session and tried to bring up the database in my web browser,
>>>> I get the following error:
>>>>
>>>> {"error":"unauthorized","reason":"Authentication required."}
>>>>
>>>> I downgraded back to 0.10.1 and things are working again except that
>>>> there is now a "_users" database that keeps causing popups saying that
>>>> it's an illegal database name. Any tips for getting Desktop CouchDB
>>>> working with 0.11?
>>>
>>> Hm. That's a little worrying. Couch has been moving from defining users
>>> in the ini file to defining users in Couch itself (in the _users
>>> database, hence your error). Jan, or other Couch people, have ini
>>> definitions entirely gone away?
>>>
>> No you can still define admins in ini.
>
> Has anyone come up with a solution for this? Apps like Gwibber
> connect to CouchDB just fine, but Futon still refuses to work. I've
> updated desktop-couch to 0.6.4 but no luck... Anything else that I
> can try before I downgrade to 0.10.2? I have some time to get back to
> developing my couchdb-using app but not having Futon available for
> debugging/experimenting makes development pretty painful.
>
This is a very odd setting, and should only be configured this way in enterprise deployments, as it makes it impossible to use the CouchDB API to signup with a CouchDB user account. It is designed for cases where users are authenticating to CouchDB via a single-signon system that is integrated in some custom deployment.
If this is configured by default in Ubuntu, then we'll need to do some work to make CouchDB usable (perhaps Ubuntu could have a service which helps with CouchDB login.) I'm hoping this isn't configured by default in Ubuntu, and you've just got an odd configuration some how.
Regardless, setting require_valid_user to false should make CouchDB useable again.