-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what if the session info (token and password) is stolen? #184
Comments
It's possible for users to remove all their (other) sessions. It's also valid for a limited time (although this is extended when used). A session isn't translatable to the user's actual password, so when it's expired or removed by the user it's useless. |
Yes, the use of the token is basic oauth. Also if you use ssl I don't see how the token and password could be stolen. |
thank you @micky2be and @peteruithoven. I am still having a difficulty to access couchDB using the token:password. I am running into problems when using token/password pair to sync the pouchdb/couchDB. I am getting 500 error messages. It appears that I get those only if I sign in fresh from a browser with cache cleaned, meaning pouchdb will try to access the All_doc of user "smith"'s personal DB "sldemo_todos$smith". Since $smith is not an admin user, the couch server returns 500 error. My code is as follows: constructor() { } setRemoteDb(url){
} The setRemoteDB is called when a user login is successful: superlogin.login(credentials)
''' |
How does superlogin deal with this type of security issues? I believe it has been handled, but I don't seen to find it described anywhere.
The text was updated successfully, but these errors were encountered: