That is the id, but I was referring to the "name" field.
{
"_id": "org.couchdb.user:nrst...@gmail.com",
"_rev": "1-fbc8402aa4d61bf0acd04ab8763760e4",
"name": "nrst...@gmail.com",
"type": "user",
"roles": [
]
}
That's the actual document.
On Tue, Aug 24, 2010 at 8:44 AM, Benoit Chesneau <bchesn...@gmail.com> wrote:
> On Tue, Aug 24, 2010 at 3:32 PM, Nathan Stott <nrst...@gmail.com> wrote:
>> It's saved in couch like "usern...@example.com"
>>
>> I have saved users named "nrst...@gmail.com" for example and that's
>> how it shows up in the "name" field in the user doc
>>
>> On Tue, Aug 24, 2010 at 4:43 AM, Benoit Chesneau <bchesn...@gmail.com> wrote:
>>> On Tue, Aug 24, 2010 at 8:08 AM, Nathan Stott <nrst...@gmail.com> wrote:
>>>> You can reproduce it easily using curl or a web browser. If your
>>>> username has an @ in it, you can't use URL authentication successfully
>>>> even if you url encode the username.
>>>>
>>>
>>> At the end couchdb see only the headers. So maybe it's the way the
>>> user was saved in the doc. Can you check how it is saved compared to
>>> the pparam you pass in your client or browser ?
>>>
>>> - benoît
>>
>
> I think it should be org.couchdb.user:username as id in user db. Need
> to check though.
>
> - benoit
>
