node-openid-client
okta-auth-js
node-openid-client | okta-auth-js | |
---|---|---|
3 | 5 | |
1,727 | 432 | |
- | 0.7% | |
7.7 | 7.5 | |
7 days ago | 7 days ago | |
JavaScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-openid-client
-
Are people using Auth.js already?
Nearly all of the platforms implement OpenID, so I ended up rolling my own integration using openid-client to do the third party auth, and then on success, just set your own cookie.
-
Any resources of OAuth2 without using any packages/passport.js?
There is quite a bit of hidden complexity to doing different flows. One approach to learning these is to use a lower level library (and perhaps review its code) such as the excellent openid-client.
-
[AskJS] Which JS OpenID Connect library to use in 2021?
I've successfully used this one in the past, specifically the Passport strategy. Based on a cursory search it seems like the best current option.
okta-auth-js
-
OIDC / OpenID Connect - Single/Global Logout
hmm, I think I see why I'm confusing these two methods. In the context of using the okta-auth-js library.
-
Migrating from Create React App (CRA) to Vite
Answer: This often happens when you're using a library with a umd bundle, where Vite expects an ESM bundle. This happened to me with okta-auth-js and the fix was to specifcally tell Vite to load the umd bundle in the Vite config file:
-
Getting lots of 'Failed to execute 'postMessage' on 'BroadcastChannel': Channel is closed' errors
https://github.com/okta/okta-auth-js/issues/1194 might be related?
- [AskJS] Which JS OpenID Connect library to use in 2021?
-
Has anyone used Okta + react testing library?
I've implemented auth using okta-react and okta-auth-js and everything works. However, I've now turned to the testing side using React Testing Library and I was wondering if anyone here has experience with using it with these Okta libraries? Do I have to mock an authenticated user?
What are some alternatives?
node-oidc-provider - OpenID Certified™ OAuth 2.0 Authorization Server implementation for Node.js
okta-react - Okta OIDC SDK for React
passport-steam - Steam (OpenID) authentication strategy for Passport and Node.js.
vite-tsconfig-paths - Support for TypeScript's path mapping in Vite
vite-plugin-svgr - Vite plugin to transform SVGs into React components
angular-auth-oidc-client - npm package for OpenID Connect, OAuth Code Flow with PKCE, Refresh tokens, Implicit Flow
create-vite-app - Create a Vite-powered app in seconds!
Ory Hydra - OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid.
vite - Next generation frontend tooling. It's fast!
tidal-connect-docker - This is the dockerized version of Tidal Connect Raspberry binairies. Can be seemlessly used in HifiberryOS or any other RPi based operating system running Docker.
passport-facebook - Facebook authentication strategy for Passport and Node.js.