Configure an authentication challenge policy in PingAccess to set the response that PingAccess sends when it receives unauthenticated requests for protected resources.
- Click Access and then go to .
- Click + Add Authentication Challenge Policy.
- In the Name field, enter a unique name for the authentication challenge policy.
- Optional: In the Description field, enter a description for the authentication challenge policy.
In the Challenge Response Mapping list, select a mapping
The MS-OFBA challenge response mapping examines
OPTIONS HTTPmethod requests to determine if the user agent is a client that supports Microsoft's MS-OFBA protocol or if the request has a Boolean flag indicating that it supports MS-OFBA.Tip:
PingAccess provides an MS-OFBA authentication challenge policy that's included with the system by default. As such, the MS-OFBA challenge response mapping is best used to address edge cases as they come up. For more information, see Authentication.
If you selected the Content Negotiation mapping
type, in the Media Types list, select one or more
The selection options for media types are application/json, text/html, text/plain, or text/xml.
Acceptheader field in the request matches any of the specified media types, the mapping is applied.
If you selected the Header Fields mapping type,
click + Add Row to add one or more rows, and then
in the Name and Value
Pattern fields, enter a name and value pattern for each
If all of the specified header fields in the request match the specified value patterns, the mapping is applied.
- If you selected the Content Negotiation mapping type, in the Media Types list, select one or more media types.
Configure a challenge response generator for the challenge response
In the Challenge Response Generator list, select
a challenge response generator.
For more information, see Authentication challenge responses and Authentication challenge response generator descriptions.
If you selected Browser-handled OIDC Authentication
Request, HTML OIDC Authentication
Request, MS-OFBA Authentication Request
Redirect, OIDC Authentication Request
Redirect, or PingFederate Authentication API
Challenge, you can select one of the following options
from the Prompt Request Parameter list to let the
authorization server know whether to prompt an end-user to
reauthenticate or provide consent.
- Returns an error if the end-user isn't authenticated or if
OAuth clientdoesn't have user consent for the requested claims. The authorization server doesn't prompt the end-user with a consent or authentication page if this option is selected. OAuth client The application in an OAuth framework that requests access to resources. If the request is approved by the authorization server, the client is issued an access token for the resources.
- The authorization server prompts the end-user to
reauthenticate. If the end-user doesn't reauthenticate
successfully, it returns an error.Note:
For extra security, PingAccess validates the <auth_time> the login request was sent at against the <auth_time> the
OpenID Provider (OP)sets in the response. OpenID Provider (OP) OP In OAuth terms, an authorization server (AS). The OP/AS issues access tokens to protected resources for approved clients (relying parties). The clients use the access token to access the protected resources hosted by the OAuth resource server.
- The authorization server prompts the end-user for consent before giving information to the OAuth client. If the end-user doesn't give their consent, it returns an error.
- The authorization server prompts the end-user to specify which account they are using, in case they have multiple accounts. If the end-user doesn't select an account, it returns an error.
If you are using PingFederate as the OP, you should also enable push authorization requests on the web session you want to use with this authentication challenge policy. This advanced setting provides an additional layer of security against frontchannel tampering. For more information, see Enable Push Authorization in Creating web sessions.Note:
You can set the Prompt Request Parameter in two places: on the web session or on one of the
OpenID Connect (OIDC)authentication challenge response generators. A value set on a specific authentication challenge response generator takes precedence over one set on a web session. OpenID Connect (OIDC) OIDC An authentication protocol built on top of OAuth that authenticates users and enables clients (relying parties) of all types to request and receive information about authenticated sessions and users. OIDC is extensible, allowing clients to use optional features such as encryption of identity data, discovery of OpenID Providers (OAuth authorization servers), and session management.
If you selected OIDC Authentication Request
Redirect, Redirect Challenge, or
Templated Challenge, you can configure
to let the authentication authority know why a user was redirected to
- Go to the Web Sessions page and expand the
web session that you want to edit.Important:
If you selected Redirect Challenge, make sure that you select the Append Redirect Parameters check box in step 6d.
If you selected Templated Challenge and are using PingFederate as an authentication source, make sure that you connect to PingFederate's redirectless OIDC flow.
- Click the Pencil icon, and then select the Provide Authentication Feedback check box under Advanced Settings.
For more information about the feedback PingAccess can provide, see Creating web sessions.
An OIDC Authentication Request Redirect issues the feedback key vnd_pi_authn_feedback. The feedback key issued by an Redirect Challenge is authnFeedback, and the feedback key issued by an Templated Challenge response generator is oidc.authnFeedback.
- Go to the Web Sessions page and expand the web session that you want to edit.
If you selected Redirect Challenge, enter a
Redirect URL and select a Response
Code for the redirect.
- In the Challenge Response Generator list, select a challenge response generator.