--- title: Download manifest description: The following files are included in the latest version of the PingOne MFA Integration Kit .zip archive: component: pingone page_id: pingone:pingone_mfa_integration_kit:pf_p1_mfa_ik_download_manifest canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_mfa_integration_kit/pf_p1_mfa_ik_download_manifest.html revdate: February 13, 2026 --- # Download manifest The following files are included in the latest version of the PingOne MFA Integration Kit `.zip` archive: * `Legal.pdf`: Copyright and license information. * `dist/pingfederate/server/default`: Contains the integration files. * `lib/pf-authn-api-sdk-.jar`: A `.jar` file containing the PingFederate Authentication API SDK. * `deploy/pf-pingone-mfa-adapter-.jar`: A `.jar` file containing the PingOne MFA IdP Adapter, PingOne MFA Remember Me Verifier Adapter, and PingOne MFA Remember Me Manager Adapter. * `conf`: Contains the HTML template that presents the PingOne sign-on form. * `template`: Contains user-facing HTML template files. * `assets`: Contains functional scripts and files used by the template. * `scripts`: Contains script files used to collect and send information. * `jquery-.min.js`: A JavaScript file that contains the jQuery library. * `jquery-qrcode.min.js`: A JavaScript file that generates QR codes. * `signals-sdk-.js`: A JavaScript file that generates the signals payload required to create and verify Remember Me devices. | | | | - | ---------------------------------------- | | | Make sure to use version 5.6.3 or later. | * `images`: Contains template image files. * `icons`: A collection of icons used in the template file. * `flags.png`: A collection of flags for internationalization. * `ping-logo.png`: An image file with company branding. * `ping-logo.svg`: An image file with company branding. * `spinner-alt.svg`: An image file used in a spinner animation. * `spinner.svg`: An image file used in a spinner animation. * `fonts/end-user/icons`: Contains template icons. * `data`: Contains JSON files used by the templates. * `CountriesWithCountryCode.json`: A JSON file that enables use of the country prefix selector on the **Device Selection** page. * `css`: Contains `.css` files for the templates. * `end-user//end-user.css`: A `.css` file that customizes the appearance of the template files. * `pingone-mfa.css`: A `.css` file that customizes the appearance of the template files. * `pingone-mfa-assertion-required.html`: A sample template that indicates a request has been sent to a FIDO2 device. * `pingone-mfa-authentication-code-response-required.html`: A sample template that prompts the user to enter an authentication code. * `pingone-mfa-completed.html`: A sample template that indicates the multi-factor authentication (MFA) *(tooltip: \
\

An electronic authentication method where a user is granted access only after presenting two or more verification factors for authentication.\

\
)* step completed successfully. * `pingone-mfa-device-locked.html`: A sample template that informs the user their device has been locked. * `pingone-mfa-device-pairing-method-failed.html`: A sample template that indicates the device pairing method failed on the server side. * `pingone-mfa-device-pairing.html`: A sample template that allows the user to pair an MFA device. * `pingone-mfa-device-selection.html`: A sample template that allows the user to select the MFA device they want to use. * `pingone-mfa-failed.html`: A sample template that indicates the MFA step failed. * `pingone-mfa-fido2-device-activation.html`: A sample template that prompts the user to activate a FIDO2 device. * `pingone-mfa-mobile-activation.html`: A sample template that prompts the user to activate a mobile device. * `pingone-mfa-oath-token-activation.html`: A sample template that prompts the user to activate an OATH token device. * `pingone-mfa-oath-token-pairing.html`: A sample template that prompts the user to select an OATH token to use for MFA. * `pingone-mfa-offline-device-activation.html`: A sample template that prompts the user to activate an offline MFA device. * `pingone-mfa-offline-device-pairing.html`: A sample template that prompts the user to enter an offline device to use for MFA. * `pingone-mfa-one-time-device-selection.html`: A sample template that prompts the user to select a one-time device to authenticate with. * `pingone-mfa-otp-required.html`: A sample template that prompts the user to enter a one-time passcode. * `pingone-mfa-push-confirmation-rejected.html`: A sample template that indicates an MFA push was rejected. * `pingone-mfa-push-confirmation-timed-out.html`: A sample template that indicates an MFA push timed out. * `pingone-mfa-push-confirmation-waiting.html`: A sample template that indicates the adapter is waiting for a response to an MFA push. * `pingone-mfa-remember-me-spinner.html`: A sample template that the server renders in the user's browser to collect their device information. * `pingone-mfa-remember-me-user-consent.html`: A sample template that prompts the user to choose whether the PingOne MFA Integration Kit should remember the device they're currently using. * `pingone-mfa-setup.html`: A sample template that prompts the user to set up an MFA device. * `pingone-mfa-totp-device-activation.html`: A sample template that prompts the user to activate a timed one-time password (TOTP) device. * `pingone-mfa-update-nickname`: A sample template that prompts the user to enter a nickname for the specified device. * `language-packs`: Contains files with customizable user-facing messages. * `pingone-mfa-messages.properties`: A variable file that customizes the messages that appear on the template file.