---
title: Configuring multi-version adapter support
description: Configure the PingOne MFA Integration Kit 2.7.1 and 3.0 adapters to run at the same time, serving different application versions without compatibility issues.
component: pingone
page_id: pingone:pingone_mfa_integration_kit:pf_p1_mfa_ik_configuring_multi_version_adapter_support_4.0
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_mfa_integration_kit/pf_p1_mfa_ik_configuring_multi_version_adapter_support_4.0.html
llms_txt: https://docs.pingidentity.com/integrations/pingone/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: August 26, 2025
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result
---

# Configuring multi-version adapter support

Configure the PingOne MFA Integration Kit 2.7.1 and 3.0 adapters to run at the same time, serving different application versions without compatibility issues.

|   |                                                                                                                                                                                                                                                                                                                                                       |
| - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This is a temporary solution during the transition period from 2.7.1 to 3.0. Note the following about multi-version adapter support:- The only supported version combination is 3.0 and 2.7.1.

- Support will only last one year.

- Multi-version adapter support won't be compatible with future releases or made available for previous releases. |

## About this task

PingOne MFA Integration Kit 3.0 introduces breaking changes to UI and API device management, making it incompatible with previous versions. Running a previous adapter version at the same time as the 3.0 adapter enables you to slowly transition to 3.0 as you navigate the new device management behavior.

|   |                                                                                                         |
| - | ------------------------------------------------------------------------------------------------------- |
|   | PingFederate doesn't allow multiple versions of the same adapter to coexist within a single deployment. |

PingOne MFA Integration Kit 2.7.1 is a version of the 2.7 adapter that's been modified through shading, so it can be deployed alongside 3.0. This enables you to run both versions at the same time and direct requests to the appropriate adapter instance.

## Steps

1. Deploy and configure the 3.0 and 2.7.1 adapters:

   1. Deploy and configure the 3.0 adapter instance as described in [PingOne MFA IdP Adapter settings reference](pf-p1-mfa-ik-p1-mfa-idp-adapter-settings-reference_4.0.html):pf_p1_mfa_ik_deploying_the_integration_files.adoc\[] and [Configuring an adapter instance](pf_p1_mfa_ik_configuring_an_adapter_instance_4.0.html).

   2. For the 2.7.1 adapter instance, move only the `pf-pingone-mfa-adapter-2.7.1.jar` file into the `<pf_install>/pingfederate/server/default/deploy` directory, then configure the adapter instance as usual. Leave aside the `.html` and `.properties` files for step 2.

   |   |                                                                                                                                                                                                                                                                             |
   | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | Make sure both the `pf-pingone-mfa-adapter-3.0.jar` and `pf-pingone-mfa-adapter-2.7.1.jar` files are in the `<pf_install>/pingfederate/server/default/deploy` directory after you've finished. These `.jar` files are what enable you to create separate adapter instances. |

2. (Optional) Configure the 2.7.1 and 3.0 instances to render their respective UI versions by making the following changes to the 2.7.1 adapter configuration:

   1. In the **HTML Template Prefix** field, enter a unique prefix for 2.7.1.

      For example, `pingone-mfa-deprecated`. Learn more about this field in [PingOne MFA IdP Adapter settings reference](pf-p1-mfa-ik-p1-mfa-idp-adapter-settings-reference_4.0.html):pf_p1_mfa_ik_p1_mfa_idp_adapter_settings_reference_4.0.adoc\[].

   2. In the **Messages Files** field, enter a unique messages file name for 2.7.1.

      For example, `pingone-mfa-deprecated-messages`. Learn more about this field in [PingOne MFA IdP Adapter settings reference](pf-p1-mfa-ik-p1-mfa-idp-adapter-settings-reference_4.0.html):pf_p1_mfa_ik_p1_mfa_idp_adapter_settings_reference_4.0.adoc\[].

   3. Rename the `.html` and `.properties` files for 2.7.1 according to the prefixes you chose previously.

   4. Move the renamed files into the `<pf_install>/pingfederate/server/default/deploy` directory.

3. Set up authentication policy rules for 2.7.1 and 3.0:

   1. Differentiate 2.7.1 and 3.0 client requests based on the **Authentication Source**.

      ![Screen capture of the Authentication Source list with Tracked HTTP Parameters as an option.](_images/pf_p1_mfa_ik_tracked_parameters.png)

      For example, you could configure tracked parameters in OIDC requests. Learn more in [Defining authentication policies](https://docs.pingidentity.com/pingfederate/12.3/administrators_reference_guide/pf_defining_auth_policies.html) in the PingFederate documentation.

   2. Route traffic based on the parameter you set in step 3a.

      For example, if the value of a tracked parameter named `appVersion` is `latest`, route traffic to the 3.0 adapter. If the value of `appVersion` is anything else, route traffic to the 2.7.1 adapter.

      Learn more in [Configuring rules in authentication policies](https://docs.pingidentity.com/pingfederate/12.3/administrators_reference_guide/pf_config_rules_auth_policies.html) in the PingFederate documentation.

## Result

Both `.jar` files, application versions, and associated UI resources can now coexist without conflicts.
