Peter Uithoven
Peter Uithoven
Superlogin has configuration to create design docs (defined in files) to public and private databases. This enables including this code in version control, use linting tools, our own IDE's etc....
We're noticing that failed logins attempts are a big source of confusion for users, especially when combining multiple providers (facebook, google, local). Currently, when a user enters an invalid username/E-mail...
I understand an email can contain both a html and a plain text version. Where the users email client decides which one is shown. - https://litmus.com/blog/best-practices-for-plain-text-emails-a-look-at-why-theyre-important - http://group-mail.com/html-email/how-to-create-a-multi-part-mime-email-html-and-plain-text/ [Nodemailer](https://nodemailer.com/about/) makes...
On the client we'd like to detect when it's a good moment to refresh the session. Currently we only have a `issued` date (which is set to the date of...
A user might have selected his/her perfect username, but then make a typo in the E-mail address. In this case the user can't confirm the account, and the username is...
See: https://github.com/colinskow/superlogin/issues/162
It's a bit silly, but I was having problems getting started with the tests, this should enable people to get going quicker.
Superlogin currently seems to authorizes / deauthorizes databases per user (session). When running for example removeExpiredKeys it queries the userDocs for expired keys, collects those per user and then goes...
I was having a hard time figuring out how to add a `validate_doc_update` to a design doc, this would have answered my question.
For clarity I decided to move my `nobody` / unauthorized users question I asked in https://github.com/colinskow/superlogin/issues/152 here. When using the Cloudant authorization model each db's `_security` document contains API Keys...