BlazorIdentity
oidc-client-ts
BlazorIdentity | oidc-client-ts | |
---|---|---|
4 | 7 | |
134 | 1,205 | |
- | 4.3% | |
0.0 | 9.3 | |
over 1 year ago | 1 day ago | |
C# | TypeScript | |
MIT License | Apache License 2.0 |
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.
BlazorIdentity
- Asp.NET Identity Usermanager/RoleManager/SignInManager in Blazor Server
- Blazor identity
-
Blazor WASM and Duende (IdentityServer) - Custom Login pages
This is interesting - it's a proof-of-concept showing how the tedium of scaffolding MVC pages for login might work if it was done 'properly' in Blazor: https://github.com/DamianEdwards/BlazorIdentity
-
Is auth WAY too hard in .NET?
This might also be of interest https://github.com/DamianEdwards/BlazorIdentity
oidc-client-ts
- I can't persuade our lead software architecture that this is not going to work
-
Spring + VueJS: What's the best way to implement security?
Most recommended way is using OAuth2 + OpenId Connect. You'll need an authentication provider like keycloak, Auth0, AWS Cogito etc... Then it's just configuring Spring OAuth Resource Server and using either the vendors js library or oidc-client-ts on the frontend.
-
Auth with multi-domain/multi-tenantency in Nextjs?
Anyone has done this with OAuth in Nextjs app? I'm looking for a SSR solution. right now i'm using https://github.com/authts/oidc-client-ts. it works great for client side rendering app. but with next 13 moving everthing server side I started using next-auth. it has support to host multi-domain app in vercel but if you want to host youself it is not possible right now. I'm doing too many hacks to getting it to work right now. https://github.com/nextauthjs/next-auth/issues/600 look here of the more discussion regarding this. so my question is there any other way to do oauth in nextjs 13 in multidomain usecase?
-
(React/.NET) How to implement OAuth in a fullstack application? (my implementation in the description)
I generally use https://github.com/authts/oidc-client-ts which wires it up for you.
-
JWT storage best practices
How does that work with oidc and refresh tokens etc? I mainly use some out of the box library to manage this https://github.com/authts/oidc-client-ts
-
vuejs google,linkedin signup
Oidc client ts (https://authts.github.io/oidc-client-ts/) for oauth2 authentication
- Is auth WAY too hard in .NET?
What are some alternatives?
oidc-client-js - OpenID Connect (OIDC) and OAuth2 protocol support for browser-based JavaScript applications
oidc-client - Light, Secure, Pure Javascript OIDC (Open ID Connect) Client. We provide also a REACT wrapper (compatible NextJS, etc.).
Blazor-WASM-Identity-gRPC - Blazor WASM, IdentityServer4 with Multiple Roles, Additional User Claim(s) & gRPC Roles Authorization
react-oidc-context - Lightweight auth library based on oidc-client-ts for React single page applications (SPA). Support for hooks and higher-order components (HOC).
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
JHipster.NET - JHipster.NET blueprint
spring-authorization-server - Spring Authorization Server
fusionauth-jwt - A simple to use Java 8 JWT Library. Verify, Sign, Encode, Decode all day.
next-auth - Authentication for the Web.
breeze - Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind.