From 13261c12ef6981de010c27989812ce932cba2ebd Mon Sep 17 00:00:00 2001 From: maliming Date: Thu, 12 Mar 2026 15:38:52 +0800 Subject: [PATCH] Update article title to private_key_jwt (ABP 10.3) --- .../2026-03-12-OpenIddict-private-key-jwt-with-JWKS/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2026-03-12-OpenIddict-private-key-jwt-with-JWKS/POST.md b/docs/en/Community-Articles/2026-03-12-OpenIddict-private-key-jwt-with-JWKS/POST.md index 94cee35ccd..e5addb7521 100644 --- a/docs/en/Community-Articles/2026-03-12-OpenIddict-private-key-jwt-with-JWKS/POST.md +++ b/docs/en/Community-Articles/2026-03-12-OpenIddict-private-key-jwt-with-JWKS/POST.md @@ -1,4 +1,4 @@ -# Passwordless Client Authentication in ABP: Using JWKS with OpenIddict +# Secure Client Authentication with private_key_jwt in ABP 10.3 If you've built a confidential client with ABP's OpenIddict module, you know the drill: create an application in the management UI, set a `client_id`, generate a `client_secret`, and paste that secret into your client's `appsettings.json` or environment variables. It works. It's familiar. And for a lot of projects, it's perfectly fine.