Lance Ivy

It just needs an integration file to configure the endpoints and provide a function that fetches a user's email after signup. Here are the current examples: https://github.com/keratin/authn-server/tree/master/lib/oauth

Hello! Twitter has not been implemented yet. If you or anyone else reading this thread is interested in contributing a pull request, the requirements are roughly: 1. add a new...

Sorry, I'm not clear on the issue. AuthN implements most of the 3-legged OAuth2.0 flow. It only requires a custom function to find basic user information at the end, after...

Yep! I'm noticing a pattern in requests for some kind of event bus. I think it would be a good extension point for AuthN, and could replace the webhooks that...

@rafamel let's continue the discussion on #112

In response to https://github.com/keratin/authn-server/issues/112#issuecomment-518760094: Apologies for trying to merge this with an issue related to an event bus. Hooks are meaningfully different! I have a few points of caution here,...

@silasdavis Yes! I agree that MFA is in scope and TOTP is a good place to start. Eventually I'd like to also support delivered codes (email or SMS), so it'd...

> We might be able to defer [compulsory MFA logins] but probably worth having a vague idea. Yeah, it's worth peeking ahead. For example, if MFA is implemented as a...

The APIs necessary to add MFA to an account

@thenhawke thanks for taking the lead on this! i'll respond further in your pull request when i've had a chance to study it.