Apache Agent information
The Apache Agent lets your Apache server communicate with PingFederate. When a user tries to access a resource on your Apache server, the agent checks their session status. When a user starts a new session, the agent validates OpenToken information from PingFederate and lets the user access the resource.
SSL support
The Apache Agent supports TLS/SSL, using standard Apache SSL support for connections to the server from browsers.
Session validation
PingFederate validates both an inactivity timeout and an overall session timeout:
- Inactivity timeout
-
The amount of time that a session can be inactive (no new browser requests are received) before a user is required to re-authenticate.
- Overall session timeout
-
The total amount of time that a session can be active, regardless of activity, before the user is required to re-authenticate.
If either of the timeout limits has expired, the Apache Agent cancels the existing session and redirects the browser to the PingFederateLoginPageUrl address in your <apache_home>/conf/mod_pf.conf file. This starts a service provider (SP)-initiated single sign-on (SSO) request at the identity provider (IdP).
|
Session cancellation enforces session cleanup in the PingFederate server and obsolescence of session cookies. |
Memory usage
The Apache Agent uses the Apache Portable Runtime (APR) pools for allocation of most data: either the configuration-time pool for storing configuration variables or request-time pools for processing sessions.
Heap is used only for temporary data with a short usage time and sensitive size, such as:
-
Dynamic reallocations on compressed-token decompression
-
Parsing session information
-
Operations with the OpenToken library
Session information and user attributes
The PingFederate Apache Agent passes session information and user attributes from the adapter to the application.
The Apache Agent includes the information in HTTP request headers or Apache environment variables. This information can then be used by the application for authorization decisions or for generation of content specific to the user making the request.
The following session and attribute information is exposed to the application:
- Attributes from the OpenToken Adapter contract
-
The subject (
SUBJECT) and any attributes that you add on the Extended Contract tab of the adapter configuration. Only the attributes fulfilled at runtime are exposed to the application; attributes with aNULLvalue are not included in the OpenToken. NOT-ON-OR-AFTER-
The time until inactivity timeout is reached.
RENEW-UNTIL-
The time until overall session timeout is reached.
AUTH_NOT-BEFORE-
The time when the session was created.
AUTHNCONTEXT-
Information from the SAML assertion that describes how the user was authenticated at the IdP.
For security reasons, each HTTP request header or Apache environment variable is first pre-pended with a specific prefix. For help configuring the prefix, see Configuring the Apache Agent. The Apache Agent always removes and rewrites these prefixed request headers and/or environment variables for each request.
If you can’t modify your applications to accept headers with this prefix, you can configure the Apache Agent to add a prefix to the HTTP headers or environment variables. In this case, on the Extended Contract tab of the OpenToken Adapter configuration, include an attribute named pf_attribute_list. Map that attribute in your identity provider (IdP) connection as a text field containing a comma-separated list of all the attributes in the adapter contract. This attribute list is sent in the OpenToken and used by the Apache Agent to overwrite headers in the request.
For more information, see Configuring target session fulfillment in the PingFederate documentation.
Error handling
When an error occurs, the Apache Agent redirects the browser to the PingFederateErrorPageURL address in your <apache_home>/conf/mod_pf.conf file.
|
This value isn’t enabled by default, but examples are provided. |
Session logout
The PingFederateCancelURL address in your <apache_home>/conf/mod_pf.conf file initiates a user-session logout. This URL specifies a resource that directs the Apache Agent to:
-
Initiate a single logout (SLO) (if configured to do so)
-
Expire the PingFederate session
-
Clean up any resources associated with the session
-
Pass control back to the application so that it can clean up its own session
Logging
The PingFederate Apache Agent uses an Apache API logging scheme that writes into the standard logs/error_log file. This file is created automatically at startup with the verbosity level controlled by LogLevel in your httpd.conf file.
The PingFederate Apache Agent has six internally distinguished verbosity levels, ranging from 0 to 5. The first four correspond to Apache definitions in error/warn/notice/info. The last two levels are for logging HTTP requests/responses and cURL-library debug output, if necessary. The default level is 0, which logs only errors.
|
The Apache Agent logs all of its output at the |