Ping-federate (Section)#
Path: /profiles/profile{id, type}/settings/authentication-service/protocols/protocol{id}/ping-federate
A Protocol plugin using Pingfederate’s agentless adapter integration method
Parameters#
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| dropoff-url | uri | required | ||
| dropoff-username | string | required | ||
| dropoff-password | string | required | ||
| idp-adapter-id | string | required | ||
| server-base-url | uri | required | ||
| http-client | leafref | required | ||
| allowed-origins | multi-value, non-empty-string | optional | When PingFederate is requesting authentication directly, this optional list of URI’s or URI-patterns define which origins are allowed to frame pages in, i.e. this list decides how and which allowed frame response headers are sent. If none are configured, framing is not allowed for this protocol. Note that when PingFederate includes a client_id, the ServiceProvider’s framing settings are used! | |
| application-url | uri | optional | This URL is used if a request is made to the authentication service without the parameters necessary to initiate an authentication transaction. In such a case, the user is redirected to this URL, so that a new, properly formed, request can be made to bootstrap a new authentication transaction. When integrating to PingFederate, this could happen, for example, if the user arrives at the authentication service via PingFederate, book marks the page, and later follows their new bookmark. In this case, the user would not see an error page, but instead be redirected to this URL. |