---
title: Tracking transactions between PingFederate and PingAM
description: To help with application log debugging, you can track PingFederate and PingAM transactions using a unique request ID that's set by the adapter.
component: pingam
page_id: pingam:troubleshooting:pf_pingam_ik_tracking_transactions
canonical_url: https://docs.pingidentity.com/integrations/pingam/troubleshooting/pf_pingam_ik_tracking_transactions.html
revdate: July 29, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result
---

# Tracking transactions between PingFederate and PingAM

To help with application log debugging, you can track PingFederate and PingAM transactions using a unique request ID that's set by the adapter.

## About this task

PingFederate and PingAM both have methods to keep track of transactions across multiple applications:

* In PingFederate, the `httprequestid` can be used to track transactions that come from outside PingFederate.

* In PingAM, the [`X-ForgeRock-TransactionId` header](https://docs.pingidentity.com/pingam/latest/am-rest/rest-intro.html#x_forgerock_transactionid) tracks related requests throughout the ForgeRock platform.

To track transactions between PingFederate and PingAM, the PingAM IdP Adapter injects the `X-ForgeRock-TransactionId` header with the `httprequestid` value in all API calls to PingAM.

Complete the following procedure to finish the setup in PingAM and see the unique request ID in the audit logs:

## Steps

1. To see the value set for `httprequestid` in the `X-ForgeRock-TransactionId` header, configure PingFederate to log the `httprequestid`:

   1. In the `<pf_install>/pingfederate/server/default/conf/log4j2.xml` file, go to the `SecurityAudit2File` RollingFile and add the **httprequestid** field in the **Pattern** section.

      Learn more in [PingFederate security audit logging](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_security_audit_logging.html) and the [PingFederate log files](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_pf_log_files.html) section of the PingFederate documentation.

   2. Save the file.

2. Configure PingAM to accept the `X-ForgeRock-TransactionId` header:

   1. In the PingAM admin UI, go to **Configure > Server Defaults > Advanced** and go to the bottom of the list.

   2. In the **Property Name** column, enter `org.forgerock.http.TrustTransactionHeader`.

   3. In the corresponding **Property Value** column, enter `true`.

   4. To add the property and save your work, click the **+** icon.

### Result

You can now track the unique request ID between PingFederate and PingAM in the PingFederate security audit log and the PingAM access audit log.