4 ms·
Yeah, I don't know any other options for vanilla JS that support what you want. There are embeddable/self-hostable auth servers (FusionAuth--full disclosure, I
by mooreds 4y ago
Yeah, I don't know any other options for vanilla JS that support what you want. There are embeddable/self-hostable auth servers (FusionAuth--full disclosure, I work for them, Keycloak, Ory), but it sounds like you don't want to head down that path.
> 1. Cookie or JWT based authentication that supports MFA (OTP, email, and SMS), for clients (web/mobile) that are internal. 2. OAuth2/OIDC (again with MFA), for third-party clients, combined with API keys for identifying registered clients. 3. API keys, for secure clients who will be accessing read-only data or functionality via the API
> (if not, I'd like to know what the issues are).
For #2, if you are setting up OIDC, you typically don't get to control MFA. You're delegating the authentication event to the upstream identity source, so they control if they ask for additional factors of authentication.
For #3, would recommend the client credentials grant for your API clients, which is essentially an API key, but generates a time bound token and is therefore a bit more secure.
I don't know whether passport plugins are vetted. I suppose you could ask on the github repo: https://github.com/jaredhanson/passport https://github.com/jaredhanson/passport
I didn't see a great way to buy/find support, but maybe there's a slack/discord out there?