[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present

["Ben Cohen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721170#comment-13721170 ] 

Ben Cohen commented on COUCHDB-1356:
------------------------------------

I see the same issue in version 1.3.1.

I post the document
{
 'name': 'admin'
 'password': 'adminpass'
}

to _session to login and receive the reply:

{
 "ok":true,
 "name":null,
 "roles":["_admin"]
}

A subsequent get to _session shows that I have logged in as the correct user.

{
 "ok":true,
 "userCtx":{"name":"admin","roles":["_admin"]},
 "info":{"authentication_db":"_users","authentication_handlers":["oauth","cookie","default"],"authenticated":"cookie"}
}
                
> POST _session responds with name: null if _admin user and no _users doc present
> -------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1356
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1356
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Johannes J. Schmidt
>            Priority: Minor
>
> When logging in with admin credentials (and no corresponding _users doc, if that is important), the response of the POST to _session has the name property set to null:
>   {"ok":true,"name":null,"roles":["_admin"]}
> It should be the name of the admin instead, like it does when logging in with a standard user:
>   {"ok":true,"name":"standarduser","roles":[]}
> Requesting the _session object after logging in with an admin, the name is proper set:
> {"ok":true,"userCtx":{"name":"adminuser","roles":["_admin"]},"info":{"authentication_db":"_users","authentication_handlers":["oauth","cookie","default"],"authenticated":"cookie"}}
> Johannes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira