A company has removed the requirement to record back-channel requests from PingAccess to PingFederate in the audit log.
Where should the administrator update this behavior without affecting existing applications?
PingAccess can be configured to log or suppress back-channel requests that occur during token validation with an OAuth/OpenID Connect provider such as PingFederate. These requests happen when PingAccess calls PingFederate to validate access tokens or retrieve key material.
Exact Extract from PingAccess documentation:
''Back-channel requests are logged during token validation by default. To prevent these requests from being written to the audit log, update the Token Validation settings in PingAccess.''
This makes Token Validation the correct location for changing the behavior without modifying application-specific configurations.
Why other options are wrong:
B . Web Sessions
Incorrect. Web Sessions control user session management and cookie handling, not back-channel token validation traffic.
C . Sites
Incorrect. Sites are the definitions of backend servers that PingAccess proxies to. This setting does not affect back-channel logging to PingFederate.
D . Token Provider
Incorrect. The Token Provider defines the OIDC/OAuth server (e.g., PingFederate) and its endpoints, but the logging of back-channel requests is not controlled here.
Thus, the correct answer is A. Token Validation.
Theron
9 hours agoZona
6 days agoBasilia
11 days agoLynelle
16 days agoArtie
21 days agoAmie
26 days agoHannah
1 month agoNu
1 month agoTarra
1 month agoPamela
2 months agoMee
2 months agoJospeh
2 months agoDeonna
2 months agoDorothy
2 months agoBasilia
3 months agoEmelda
3 months agoTeri
3 months agoBettyann
3 months agoKing
4 months agoArminda
4 months agoJacinta
4 months agoStevie
4 months agoChau
4 months agoLoise
4 months agoNguyet
5 months agoChery
2 months ago