An overview of creating and configuring a Kerberos Adapter instance to integrate PingFederate with Windows clients. Create and configure an instance of the Kerberos Adapter for Windows clients to authenticate using single sign-on.
- Go to .
- On the IdP Adapters window, click Create New Instance to start the Create Adapter Instance configuration.
On the Type tab, configure the basics of this adapter
- Enter the instance name and ID.
- From the Type list, select the adapter type.
From the Parent Instance list, select an existing type.
If you are creating an instance that is similar to an existing instance, you might consider making it a child instance by specifying a parent. A child instance inherits the configuration of its parent unless overridden. You can specify overrides during the rest of the setup.
On the IdP Adapter window, configure your Kerberos Adapter
See the on-window field descriptions and the following table for more information.
Field Description Domain/Realm Name
Select your Windows domain.
If the domain or realm you want does not appear, click Manage Active Directory Domains/Kerberos Realms to add it. For more information, see Active Directory and Kerberos.
Error URL Redirect Enter a URL for redirecting the user if there are errors. This URL has an errorMessage query parameter appended to it, which contains a brief description of the error that occurred. The error page can optionally display this message on the window to provide guidance on remedying the problem.Note:
In the case of an error, if you define an Error URL Redirect and the adapter instance is included in an instance of the Composite Adapter, the user is redirected to the configured error URL rather than continuing on to the next adapter in the chain. Leave this field blank to have the adapter continue on to the next adapter.
When employing the errorMessage query parameter in a custom error page, adhere to Web-application security best practices to guard against common content injection vulnerabilities. If no URL is specified, the appropriate default error landing page appears.
Click Show Advanced Fields to review the following settings. Modify as needed.
Error Template When selected, displays a template to provide standardized information to the end user when authentication fails. The Error URL Redirect value is ignored.
kerberos.error.template.htmlin the <pf_install>/pingfederate/server/default/conf/template directory uses the Velocity template engine and can be modified in a text editor to suit your particular branding and informational needs. For example, you can give the user the option to try again if authentication fails. For more information on Velocity templates, see Customizable user-facing pages .
Authentication Context Value This can be any value agreed to with your SP partner to indicate the type of credentials used to authenticate. Standard URIs are defined in the SAML specifications. For more information on SAML specifications, see the OASIS documents oasis-sstc-saml-core-1.1.pdf and saml-authn-context-2.0-os.pdf.If left blank, PingFederate sets the authentication context as follows:
urn:oasis:names:tc:SAML:1.0:am:unspecifiedfor SAML 1.x
urn:oasis:names:tc:SAML:2.0:ac:classes:unspecifiedfor SAML 2.0
Either an instance of the Requested AuthN Context Authentication Selector or the SAML_AUTHN_CTX attribute can override the authentication context in the SAML attribute contract. The latter takes precedence.
On the Extended Contract tab, configure additional
attributes for this adapter instance as needed.
The Kerberos Adapter contract includes three core attributes: Domain/Realm Name, SIDs, and Username.
On the Adapter Attributes tab, configure the pseudonym and
The Override Attributes check box in this window reflects the status of the override option in the Extended Contract tab.
Select the check box under Pseudonym for the user
identifier of the adapter and optionally for the other attributes, if
This selection is used if any of your service provider (SP) partners use pseudonyms for account linking.Note:
A selection is required whether or not you use pseudonyms for account linking. This allows account linking to be used later without having to delete and reconfigure the adapter. Ensure that you choose at least one attribute that is unique for each user, such as a user's email, to prevent assigning the same pseudonym to multiple users.
- Select the check box under Mask Log Values for any attributes that you want PingFederate to mask their values in its logs at runtime.
- Select the Mask all OGNL-expression generated log values check box, if OGNL expressions might be used to map derived values into outgoing assertions and you want those values masked.
- Select the check box under Pseudonym for the user identifier of the adapter and optionally for the other attributes, if available.
On the Adapter Contract Mapping tab, configure the adapter
contract for this instance with the following optional workflows:
- Configure one or more data sources for datastore queries.
- Fulfill adapter contract with values from the adapter, the default, datastore queries, if configured, context of the request, text, or expressions, if enabled.
- Set up the Token Authorization framework to validate one or more criteria prior to the issuance of the adapter contract.
- On the Summary tab, review your configuration and modify as needed. Click Done to exit the Create Adapter Instance configuration window.
When finished in the IdP Adapters window, click
Save to confirm the adapter instance configuration.
If you want to exit without saving the configuration, click Cancel.