Software architect, project manager, and technical lead.
My clients rely on me to:
Currently:
Author of the Node.js Playbook (nodeplaybook.com) and currently working on Identity Desk, the complete identity solution for Node.js applications.
Let's chat about your next project: hello@farazsyed.com
Rate: USD 4000 / week (active work), USD 1000 / week (maintenance and operations retainer)
Available from September 5
Location: Toronto, Ontario, Canada
LinkedIn: https://ca.linkedin.com/in/farazsyed
GitHub: https://github.com/HiFaraz
Remote freelance and contract positions, from September 5
No blogs yet.
Writing my own :). I'm tired of implementing the same patterns again and again. In my mind the ideal library has: sensible defaults but customizable a small enough problem scope to fit majority of data stores account linking through a master user record and then each authenticator/provider defining a specific model (i.e. other fields like gender, height, friends) no-nonsense SSO (just enable a flag and become a shared identity provider to a bunch of apps) Still I think PassportJS is solid and flexible enough that the next solution should definitely be built off of it. No sense in reinventing the wheel! I asked the question here to make sure whatever I come up can help the most people! Link to my in-progress module: Identity Desk
Thanks for the response! What were the requirements for the corporate app that led you to writing your own authN code? Did you have to use the existing username/passwords for the corporate users?