hapi-routes-authorization-and-session-management
v3.0.2
Published
Provides API endpoints for HAPI servers to acquire/delete email/userid/password based sessions.
Downloads
31
Readme
(C) 2014 Martin Wawrusch
Exposes routes to aquire and destroy sessions for APIs
Dependencies:
- Requires HAPI >= 10.0.0 and hapi-oauth-store-multi-tenant
Routes exposed
POST /sessions
returns
{
"url":"http://localhost:5675/users/53dc1187ee1768a162ea4060",
"id":"53dc1187ee1768a162ea4060",
"username":"user1",
"description":"",
"identities":[
],
"profileLinks":[
],
"userImages":[
],
"emails":[
"[email protected]"
],
"roles":[
],
"data":{
},
"stats":{
},
"resourceLimits":[
],
"createdAt":"2014-08-01T22:15:35.518Z",
"updatedAt":"2014-08-01T22:15:35.518Z",
"isDeleted":false,
"deletedAt":null,
"onboardingState":null,
"primaryEmail":"[email protected]",
"needsInit":false,
"gender":"",
"timezone":0,
"locale":"en_us",
"verified":false,
"token":{
"accessToken":"53dc1187ee1768a162ea4061",
"refreshToken":"TPCID3RwjdPMDt8rwcCMIRvyCVSz00FdkiBUrkwVc3IIIU8TWTBsyjfQjgtagW6HgivNfLcvnkZQobmb"
}
}
on success with 201, otherwise 422
DELETE /sessions/me expects a token (24 char hex string, mongodb uid) in the credentials, deletes the session if exists, returns 204 on success
Change Log
3.0.0
- Most of the API is now fully validated, although the individual validation needs more fine tuning.
- BREAKING: Posting to create a session now requires a clientId, the options parameter is now ignored.
See also
- hapi-auth-bearer-mw
- hapi-loggly
- hapi-mandrill
- hapi-mongoose-db-connector
- hapi-oauth-store-multi-tenant
- hapi-routes-authorization-and-session-management
- hapi-routes-oauth-management
- hapi-routes-roles
- hapi-routes-status
- hapi-routes-users-authorizations
- hapi-routes-users
- hapi-user-store-multi-tenant
and additionally
Contributing
- Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
- Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
- Fork the project
- Start a feature/bugfix branch
- Commit and push until you are happy with your contribution
- Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
- Please try not to mess with the package.json, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
Copyright
Copyright (c) 2014 Martin Wawrusch