Our great sponsors
-
oidc-client-js
Discontinued OpenID Connect (OIDC) and OAuth2 protocol support for browser-based JavaScript applications
-
oidc-client-ts
OpenID Connect (OIDC) and OAuth2 protocol support for browser-based JavaScript applications
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
breeze
Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind. (by laravel)
-
BlazorIdentity
An exploration of recreating the ASP.NET Core Identity UI functionality in Blazor components.
-
oidc-client
Light, Secure, Pure Javascript OIDC (Open ID Connect) Client. We provide also a REACT wrapper (compatible NextJS, etc.).
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
POPIdentity
A lightweight, low-opinion, mini-library for social and third-party logins in ASP.NET Core.
-
ASP.NET Core
ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
They provide sample apps for the various OIDC workflows... https://github.com/IdentityModel/oidc-client-js/tree/dev/samples
a react login component: https://github.com/laravel/breeze/blob/1.x/stubs/inertia-react/resources/js/Pages/Auth/Login.jsx
There are good alternative such as https://fusionauth.io/ and https://www.keycloak.org/
There are good alternative such as https://fusionauth.io/ and https://www.keycloak.org/
This might also be of interest https://github.com/DamianEdwards/BlazorIdentity
https://github.com/AxaGuilDEv/react-oidc Use session storage or service worker storage. The library focus on security, simplicity and to be very ligthest as possible.
I stumbled upon this because of a Twitter thread that the algorithm suggested, with David Fowler in it. I give him a lot of credit, because he seems very patient. I wrote a little library just to take the auth secret, make the post to the third party, and get claims back to use in my own user management and auth bits. I still rely on the .Net auth cookie stuff, and the rest is not well documented. They insist that it's not tightly coupled to EF, but you won't find any docs that explain that.
Just look at the god awful mess they created in their implementations: https://github.com/dotnet/aspnetcore/tree/main/src/Security/Authentication
Well, I happen to be involved in a code generator (https://github.com/jhipster/jhipster-dotnetcore).