---
title: Agent SDK for C 3.0 (April 2025)
description: Info
component: pingaccess
version: 8.3
page_id: pingaccess:agents_and_integrations:pa_sdk_for_c_30_rn
canonical_url: https://docs.pingidentity.com/pingaccess/8.3/agents_and_integrations/pa_sdk_for_c_30_rn.html
revdate: June 23, 2025
section_ids:
  rhel-7-and-sles-12-deprecation: RHEL 7 and SLES 12 deprecation
  create-signed-jwts-for-agent-authentication: Create signed JWTs for agent authentication
---

# Agent SDK for C 3.0 (April 2025)

## RHEL 7 and SLES 12 deprecation

Info

As of Agent SDK for C 3.0, support for RHEL 7 and SLES 12 has been removed.

## Create signed JWTs for agent authentication

New PASDKC-197

The agent SDK for C now supports authenticating PingAccess agents to the engine nodes with a bearer token.

|   |                                                                                                                                                                                                                                                          |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | To use bearer token authentication, you must upgrade to PingAccess 8.2 or later and version 3.0 of either the PingAccess agent for NGINX, IIS, or Apache (RHEL or SLES). Compatibility for the Apache (Windows) agent will be added in a future release. |

After you configure a compatible PingAccess agent with the updated `agent.properties` file and select **Require Token Authentication** in the agent's configuration, the agent creates, signs, and sends a unique JWT for every authentication request.

|   |                                                                                                                   |
| - | ----------------------------------------------------------------------------------------------------------------- |
|   | The JWT expires after 2 minutes, so you must ensure you synchronize the agent and the PingAccess server's clocks. |

Learn more in the [PingAccess 8.2 release notes](https://docs.pingidentity.com/pingaccess/8.2/release_notes/pa_release_notes.html#configure-pingaccess-to-allow-agents-to-authenticate-with-a-bearer-token). You can find setup instructions in [Configuring PingAccess agents to use bearer token authentication](../../9.0/pingaccess_user_interface_reference_guide/pa_configuring_pa_agents_to_use_bearer_token_authn.html).