PingAccess Agent SDK for C release notes
These release notes summarize the changes in current and previous PingAccess Agent SDK for C updates.
|
The PingAccess Agent SDK for C no longer supports FreeBSD 8. |
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 and either the PingAccess agent for Apache (RHEL) or the PingAccess agent for Apache (SLES) 3.0. Compatibility for the other agent types 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. You can find setup instructions in Configuring PingAccess agents to use bearer token authentication.
Agent SDK for C 1.4.1 (December 2024)
Agent SDK for C 1.4 (October 2024)
Cache multiple token-types for Web + API applications
New PA-15516
If you use a Web + API application, the vnd-pi-resource-cache PingAccess agent protocol (PAAP) header now contains an additional path so Web + API applications can cache both cookie and authorization header token-types.
Learn more in the Cache multiple token-types for Web + API applications entry in the PingAccess 8.1 release notes.
Block bad characters
New PAA-251
Configure an agent to block requests that contain bad characters in the URI, query parameters, form parameters, or request body without having to reach out to PingAccess for a decision.
Added eight new properties to each agent:
-
agent.request.block.xss.characters -
agent.request.block.uri.characters -
agent.request.block.query.characters -
agent.request.block.form.characters -
agent.request.block.xss.http.status -
agent.request.block.uri.http.status -
agent.request.block.query.http.status -
agent.request.block.form.http.status
|
For large scale or more complex blocking decisions, it’s best practice for the agent to reach out to PingAccess for a decision. |
Ignore CRL checking if revocation server is unresponsive
Improved PAA-265
Added a new configuration option to give protected applications better reliability without giving up the ability to perform CRL checking when the server is available: the agent.engine.configuration.checkCertRevocation.bestEffort property.
This change provides better alignment between PingAccess, PingFederate, and PingAccess policy server CRL checking.
|
To use the |
Agent SDK for C 1.1.1 (January 2017)
Workaround for Network Security Services library known issue
Info
Established a workaround for a known issue in the Network Security Services library that results in a memory leak when the agent closes a HTTPS connection to a PingAccess policy server. For more information, see this KB article.