PingAccess agent for NGINX release notes
These release notes summarize the changes in current and previous PingAccess agent for NGINX updates.
PingAccess agent for NGINX 2.2 (December 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, and the agent.cache.defaultTokenType property on the NGINX agent configuration page.
|
Existing agent environments ignore the new To see the performance boost, upgrade to PingAccess 8.1 or later and upgrade to the latest version of the NGINX agent. Otherwise, continue to use an earlier agent version. |
Block bad characters in NGINX agent deployments
New PAA-251
Configure the PingAccess agent for NGINX to block requests that contain bad characters in the URI, query parameters, form parameters, or request body without reaching out to PingAccess for a decision.
Added eight new properties to the 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
Learn more in the NGINX agent configuration page.
|
For large scale or more complex blocking decisions, it’s best practice for the agent to reach out to PingAccess for a decision. |
PingAccess agent for NGINX 2.0 (February 2019)
Use the NGINX HTTP stack to communicate with PingAccess policy servers
Improved
The PingAccess Agent for NGINX now leverages the built-in, event-driven HTTP stack in NGINX to communicate with PingAccess policy servers. Previously, the agent used its own HTTP client (implemented with libcurl) to communicate with PingAccess policy servers. In certain cases, this architecture lead to poor scalability. By using NGINX’s built-in, event-driven HTTP stack, the agent is able to achieve superior scalability over previous versions.