PingAccess uses Identity Mappings to take identity attributes provided by the authentication source (e.g., PingFederate, OpenID Connect) and map them into HTTP request headers for back-end applications.

Exact Extract:

''An identity mapping allows you to map identity attributes from the user's session to HTTP headers, cookies, or query parameters that are then forwarded to the target application.''

Option A (Site Authenticators) is incorrect because Site Authenticators configure how PingAccess communicates with applications requiring authentication, not how attributes are inserted into headers.

Option B (Identity Mappings) is correct --- this is the feature designed specifically to expose user attributes to applications via HTTP headers.

Option C (Web Sessions) manages how sessions are stored and validated, but not the mapping of attributes into requests.

Option D (HTTP Requests) refers to request/response processing rules, but attributes are not mapped here.