(no title)
aurecchia | 6 months ago
Regardless, the last time I dug into this topic I ended up feeling the same. The web is littered with articles that scratch the surface and only cover the basics. They often leave out the details, which IME ended up making things more difficult to understand. What was the most helpful, as you said, was to follow the RFCs and the OIDC spec directly.
What might also be useful, if you are implementing an auth server, is to look at existing implementations. Duende IdentityServer (https://github.com/DuendeSoftware/products/tree/main/identit...) is the most widely-used one in the .NET space.
olavgg|6 months ago
I still used Spring Sessions though, where a successfull authed user got a new Spring Session. The reason was that I liked the idea of having beans with session scope, for example where each user/role has access to a specific database schema.
peterldowns|6 months ago
commandlinefan|6 months ago
And OAuth has somehow managed to be _harder_ to integrate with an existing implementation of than just to implement from scratch.
gethly|6 months ago
mettamage|6 months ago