STRENGTHENING PRE-AUTH ENDPOINT
The interim fix 220.127.116.11-MFPF-IF202010151343 introduced a breaking change to support compatibility with older versions of the Mobile Foundation server. If your app uses any of the following SDKs - Android, iOS or Cordova version 8.0.2020101412 or higher, it is necessary to upgrade your server version to 8.0.2020101311 or a higher version.
This feature was necessitated by the APAR PH30473 STRENGTHENING PRE-AUTH ENDPOINT, which introduced changes in the communication protocol between the Mobile Foundation SDKs and the Mobile Foundation server.
In the recent versions of SDKs, the entry sdkProtocolVersion=2 is added automatically in the mfpclient property file as it is the default protocol. Do not remove this mandatory entry from the file.
If you are unable to upgrade your server, as a compatibility measure, you can choose to use the newer SDKs (version 8.0.2020101412 or higher) with an older version of the Mobile Foundation server (versions before 8.0.2020101311). Add the configuration entry in the mfpclient property file, as shown in the following samples:
Native Android apps
Add the following entry to the mfpclient.properties file:
Native iOS apps
Add the following entries to the mfpclient.plist file:
Name - sdkProtocolVersion Type - Number Value - 1
Add the following entry under the
Note - The recommended approach is to upgrade the server and not to use the compatibility configuration changes discussed in this blog.
Points to Remember
- If you see a
PROTOCOL_MISMATCH_ERROR, then check the versions of both SDK and MFP server. Modify the entry from sdkProtocolVersion=1 to sdkProtocolVersion=2.
- MFP server version 18.104.22.168-MFPF-IF202010151343 and higher includes support for both protocol version 1 and 2.
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.