Lance Ivy

Interesting. AuthN currently assumes that the client secret can be generated on startup. We'll need to update the `oauth.Provider` interface to allow for dynamic configuration so that we can create...

Yeah, that's neat! It just looks like there's no way to discover the email address yet.

@cetinsert nice, looks ready

A client can implement two levels of functionality: 1) Token verification 2) Private API methods Meeting the first level of functionality would be a good starting point for anyone approaching...

I'd love to support this in AuthN! I believe https://github.com/duo-labs/webauthn would be a good starting point to plan an integration. One thing I'm presently unclear on is whether the user...

The primary challenge I see on this feature is the question of product requirements. I've tried to scope AuthN so that it only implements clear patterns, but I've seen too...

Honestly I'm not ready for implementation details yet. Some combination of tokens and redirects should work, and there's precedent for both in existing AuthN features. However, AuthN is currently not...

Sounds like a good candidate for structured logging. Would that work for you? I don't yet have plans to add other event sinks.

Let's talk about an event system! I like the idea, but am a little cautious of setting up to support multiple protocols. So my proposal is: 1. Implement an event...

@rafamel I must apologize, I was imprecise and mixed up events with hooks. I'm going to reopen #120 as a complement to this one.