paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 41 Packages Projects Releases Wiki Activity

docs: fix doc reference links

Browse Source 
Signed-off-by: Himanshu Mishra <himanshu@orkohunter.net>
This commit is contained in:
Himanshu Mishra
2021-05-06 21:41:18 +02:00
committed by Fredrik Adelöw
parent a0949d5892
commit 46c52d0aca
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/auth/identity-resolver.md
+4 -3
View File
@@ -13,9 +13,10 @@ Backstage entity by a user. The ideas here were originally proposed in the RFC
When a user signs in to Backstage, inside the `claims` field of their Backstage
ID Token (which are standard JWT tokens) a special `ent` field is set. `ent`
contains a list of [entity references](../features/software-catalog/references),
each of which denotes an identity or a membership that is relevant to the user.
There is no guarantee that these correspond to actual existing catalog entities.
contains a list of
[entity references](../features/software-catalog/references.md), each of which
denotes an identity or a membership that is relevant to the user. There is no
guarantee that these correspond to actual existing catalog entities.
Let's take an example sign-in resolver for the Google auth provider and explore
how the `ent` field inside `claims` can be set.