Specific endpoints are needed for PingFederate or another token provider to interface with PingAccess using the OpenID Connect (OIDC) protocol.
These endpoints are available on the
agent.http.port ports defined in
This endpoint clears the browser cookie containing the PingAccess Token. This endpoint enables end users to trigger the removal of their own PingAccess Cookie from the browser they are using. The user is redirected to the logged out page. You can modify the template for this page, located at <PA_INSTALL>/conf/template/general.loggedout.page.template.html.
This endpoint does not retain any server-side state to denote log off. Additionally, unless single-logout (SLO) is selected for the token provider, this endpoint clears the cookie only from the requested host/domain, and the cookie might still exist in requests bound for other hosts/domains.
If you selected the Use Single-Logout option when configuring the token provider, this endpoint also sends a logout request to the token provider, which completes a full SLO flow.
This endpoint, along with the application virtual host, becomes the redirect URI for the token provider configuration on the client.
This endpoint is used by the token provider's JSON web token (JWT) Token Processor for signature verification. This endpoint must be used in conjunction with the configuration of a JWT token processor instance in the token provider. For more information on configuring a JWT in PingFederate, see the PingFederate documentation.
This endpoint is used by the token provider to initiate a logout from PingAccess in conjunction with SLO functionality, terminating the PingAccess tokens across domains.