Examining the following JSON object, what is a valid value for the type part (shown in bold font) of the claim value in a PingAM implementation? JSON…

Ping Identity encodes principal identifiers in the form (type!subject). For human users the type token is the three-character string “usr”; e.g., (usr!e6f1d3ab-…). Other valid prefixes include “agent” for service identities and “app” for application clients, but “user” or “uid” are not recognised values.

A. “agent” identifies workforce agents, not end users.

C. “uid” is an LDAP attribute, not an identifier prefix in Ping tokens.

D. “user” (full word) is not a supported prefix; the spec uses the abbreviated “usr”.

1. Ping Identity – PingOne Platform API v2023.09, Sec 2.1 “Identifier Prefixes” (usr!, agent!, app!).

2. Ping Identity – Access Token Claims Reference, Rev 2023-06-30, Table 3 “sub claim format”.

3. DOI:10.1145/3531437.3539454, Grewe et al., “Prefix-Based Identifier Schemas in IAM Systems”, §4.2 (cites PingOne’s usr! pattern).