From 50fca5011b8e796444b2dbfbe1396aa23a3aef66 Mon Sep 17 00:00:00 2001 From: RolandGuijt Date: Wed, 14 Aug 2024 17:02:50 +0200 Subject: [PATCH] Update IdentityServer/v7/docs/content/reference/services/profile_service.md Co-authored-by: Joe DeCock --- .../v7/docs/content/reference/services/profile_service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IdentityServer/v7/docs/content/reference/services/profile_service.md b/IdentityServer/v7/docs/content/reference/services/profile_service.md index 20b702a2..47ca557b 100644 --- a/IdentityServer/v7/docs/content/reference/services/profile_service.md +++ b/IdentityServer/v7/docs/content/reference/services/profile_service.md @@ -49,7 +49,7 @@ Models the request for user claims and is the vehicle to return those claims. It - When the [server side sessions feature]({{< ref "ui/server_side_sessions/" >}}) is enabled _Subject_ will always contain the claims stored in the server side session. - When that is not the case, it depends on the caller context: - - If the _ProfileService_ is called in the context of a grant (e.g. exchanging a code for a token) the claims stored in the grant store will be used. + - If the _ProfileService_ is called in the context of a grant (e.g. exchanging a code for a token), the claims associated with that grant in the grant store will be used. When grants are stored, by default a snapshot of the logged in user's claims are captured with the grant. - If there's no grant context (e.g. when the user info endpoint is called) the claims in the access token will be used. * ***Client***