[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present
[
https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258870#comment-14258870
]
ASF GitHub Bot commented on COUCHDB-1356:
-
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-couch/pull/16
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, 2.0.0, 1.6.1
Reporter: Johannes J. Schmidt
Assignee: Robert Kowalski
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 was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present
[
https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258869#comment-14258869
]
ASF subversion and git services commented on COUCHDB-1356:
--
Commit f6a34da73b0b1c3552b77afa037c9ae287237f87 in couchdb-couch's branch
refs/heads/master from [~robertkowalski]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=f6a34da ]
Return username on POST to /_session
When logging in with admin credentials and no user doc is
present, the name was `null`. Example:
`{ok:true,name:null,roles:[_admin]}`
closes COUCHDB-1356
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, 2.0.0, 1.6.1
Reporter: Johannes J. Schmidt
Assignee: Robert Kowalski
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 was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present
[
https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222422#comment-14222422
]
ASF GitHub Bot commented on COUCHDB-1356:
-
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-couch/pull/16
Return username on POST to /_session
When logging in with admin credentials and no user doc is
present, the name was `null`. Example:
`{ok:true,name:null,roles:[_admin]}`
closes COUCHDB-1356
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-couch
COUCHDB-1356-auth-session
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-couch/pull/16.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #16
commit e109ff8f2be5f3ea1ae221279975c9e1ef75b851
Author: Robert Kowalski r...@kowalski.gd
Date: 2014-11-23T15:34:58Z
Return username on POST to /_session
When logging in with admin credentials and no user doc is
present, the name was `null`. Example:
`{ok:true,name:null,roles:[_admin]}`
closes COUCHDB-1356
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, 2.0.0, 1.6.1
Reporter: Johannes J. Schmidt
Assignee: Robert Kowalski
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 was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present
[
https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164225#comment-13164225
]
Johannes J. Schmidt commented on COUCHDB-1356:
--
But then why is the name not null when issuing a GET request to _session like I
mentioned above?
I believe the POST response should be according to the GET response.
Btw. the couch I query is not in Admin Party mode.
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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1356) POST _session responds with name: null if _admin user and no _users doc present
[
https://issues.apache.org/jira/browse/COUCHDB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164200#comment-13164200
]
Jason Smith commented on COUCHDB-1356:
--
Hi, Johannes. I believe the userCtx.name value indicates the name of the
document in the _users database, or `null` to indicate no corresponding
document. Thus, CouchDB is communicating that this request is authorized but
not to any specific user on the server. (Something similar happens if you have
an /etc/passwd, NIS, or LDAP error; or if you remove a Unix user and look at
their old files. User and group ownership will be indicated by the underlying
integer. Both the type and value communicate information.)
CouchDB also uses null to indicate that it is in Admin Party mode. If you query
/_session without authorization data, the name will be null. If the roles
include _admin, then Admin Party mode is active.
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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
