Our great sponsors
-
Hangfire
An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
-
IdentityServer
The most flexible and standards-compliant OpenID Connect and OAuth 2.x framework for ASP.NET Core
-
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.
That aside, I know it looks like/is another case of reinventing the wheel. However, I like that approach sometimes, for some things. For me it was primarily about learning, having some fun and experimenting with different things. The project is also dead simple to be honest, basically a few endpoints that check credentials, return tokens and that's about it. The next project I was thinking of was a job runner, for which I know we have alternatives such as https://www.hangfire.io/, but I find solving that problem also challenging and fun. My strategy usually is start small, then grow if needed.
Thanks for your message. No, the idea was not to re-implement OAuth nor OpenID stuff. What I had in mind for the authentication thingy was something like this: https://laravel.com/docs/9.x/sanctum. If we want to go the OAuth/OpenID way, in .NET we have this one: https://github.com/DuendeSoftware/IdentityServer.
Related posts
- Boosting Productivity with HangFire: Streamlining Background Job Processing
- How do you save a file at the end of the day within a function that is only called at certain times?
- What can I use as a simple message bus with persistence in .NET?
- Event Bus + Job APIs
- Background Job Scheduling in .NET using Hangfire