You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when extracting entities from a token in ERS, they are named jwtentity-0 and jwtentity-1 in the entity chain. This can get confusing when trying to debug; especially for decisions triggered by kas. Add more info to the entity ID so admins know what entity is being referenced.
The text was updated successfully, but these errors were encountered:
resolves#1615
before: `jwtentity-0` or `jwtentity-1`
now includes more useful info in the entity name
```
{
"id": "jwtentity-0-clientid-tdf-entity-resolution-public",
"client_id": "tdf-entity-resolution-public",
"category": "CATEGORY_ENVIRONMENT"
},
{
"id": "jwtentity-1-username-sample-user",
"user_name": "sample-user",
"category": "CATEGORY_SUBJECT"
}
```
This is useful for parsing access decisions triggered by kas. Access
decisions only reference the entityID so, previously, it was be
difficult to know what entity it is referring to without looking through
the rest of the logs. This change should provide more context and save
debugging time.
Currently, when extracting entities from a token in ERS, they are named
jwtentity-0
andjwtentity-1
in the entity chain. This can get confusing when trying to debug; especially for decisions triggered by kas. Add more info to the entity ID so admins know what entity is being referenced.The text was updated successfully, but these errors were encountered: