"user1": {"disabled": false, "password":"passw0rd", "admin_channels": ["*"]}
$ curl -X PUT http://user1:passw0rd@localhost:4984/db/doc1 -d '{ "foo":"bar"}' -H 'Content-Type: application/json'
```
Create a users session via the ADMIN REST API
```
$ curl -X POST http://localhost:4985/db/_session -d '{ "name":"user1","password":"passw0rd"}' -H "Content-Type: application/json"
```
Response: {"session_id":"971106d126515e4e071ad05070ffc76627289c16","expires":"2015-06-28T14:51:10.961084691+01:00","cookie_name":"SyncGatewaySession"}
```
$ curl --cookie "SyncGatewaySession=971106d126515e4e071ad05070ffc76627289c16" -X GET http://localhost:4984/db/doc1
```
Response: {"_id":"doc1","_rev":"1-cd809becc169215072fd567eebd8b8de","foo":"bar"}
You can check that a valid session document exists in the DB, for your example the doc name will be:
_sync:session:2823i1826e9e2ad72af0409e0703f9bf1s9317d3
Check the expiration property to make sure the cookie is still active.
Andy