Post #1265920
2026-03-31 15:01 UTC
Everything I've built has related to some part of OAuth2 or common extensions to it, like OIDC. I like these specs, been reading and using them for years, because I find the resulting code I write is more composable. Hence the reduction in effort as our OAuth2 capabilities have expanded.
I received my first interrupt that won't require new code at all, at least to start. Another team is building a capability on another platform, on a custom sub-domain, so needs auth that will work for that.
Replies (1)
-
@cmdln@thecommandline.social 2026-03-31 15:03
I already have a working, spec compliant OIDC capability that should plug right into their set up. I am proud of this capability, it works with auto-configuring clients too using a well known configuration endpoint. I've built it twice so am very familiar and very confident. First time was temporary, to meet an aggressive deadline earlier this year. Second was porting it into its permanent home, a service I wrote in Rust solely for owning our OAuth2 capabilities.