As the EAP adapter RPMs are located in the EAP channel there is a conflicts between the 7.1 and 7.2 adapter versions. That can prevent customers from following the recommended upgrade path of upgrading RH-SSO server first then adapters second.

In more details in 7.1 the situation is:

• EAP adapter RPMs are located within the EAP channels (Channel: jb-eap-7-for-rhel-7)
• EAP adapter RPMs do NOT include the RH-SSO version (Package: eap7-keycloak-adapter)
• Server RPMs are located within a channel that includes the RH-SSO version (Channel: rh-sso-7.1-for-rhel-7, Package: rh-sso7)

Now, for 7.2 if we use the same approach customers will be upgraded to 7.2 EAP adapter RPMs automatically, but will have to manually switch the channel to upgrade the RH-SSO server itself. This conflicts with our recommendations of upgrading the RH-SSO server first and adapters second. It also prevents customers from remaining on 7.1 adapter RPMs.

The agreed solution is to add the <major>.<minor> version of the adapter to the package name.