HackerTrans
トップ新着トレンドコメント過去質問紹介求人

aaronpina

no profile record

投稿

[untitled]

1 ポイント·投稿者 aaronpina·4 か月前·0 コメント

From Demo JWT to Production JWT: Adding Proper Audience Validation in .NET

aaronpina.com
1 ポイント·投稿者 aaronpina·4 か月前·0 コメント

Lazy JWT Key Rotation in .NET: Redis-Powered JWKS That Just Works

aaronpina.com
21 ポイント·投稿者 aaronpina·4 か月前·13 コメント

The JWKS Setup for Robust JWT Validation in Asp.net 10

aaronpina.com
2 ポイント·投稿者 aaronpina·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 aaronpina·5 か月前·0 コメント

コメント

aaronpina
·5 か月前·議論
It's great that Elon has such ambitious plans, but as he keeps saying, he wants the future to look like the Culture in Iain M Bank's sci-fi series of the same name. If you read at least the first book of the series, you'll see that it's a Communist society run by AI's. I'm not really sure that's the kind of future I want to be living in. Elon's original plan just to make life multi-planetary was a much more palatable future.
aaronpina
·5 か月前·議論
Refresh tokens are essential for secure, long-lived sessions in .NET APIs, but they are surprisingly easy to get wrong. This post walks through building a simple auth server that issues short-lived JWT access tokens + opaque refresh tokens, then shows a practical client token refresh strategy: reactive refresh (automatic on 401 with DelegatingHandler). Includes full runnable code, common pitfalls, and an engaging style that reads like a magazine article. Built from first principles in .NET 10.