The development server that is used in MobileFirst Studio does not support Application Authenticity Protection. The feature is available only for applications that are deployed to an external Tomcat/WAS full profile/WAS Liberty profile.
The warning is there to let you know that you did not enable Extended Authenticity.
To enable it, you need to follow the steps as described in the following tutorial once you move to an external application server: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/authentication-security/application-authenticity-protection/
Take note of the section "Enabling extended application authenticity protection", which says the following:
To enable extended authenticity checking, you must deploy a modified
.wlapp file, instead of the original .wlapp file that is generated by
the build process.
Modify the .wlapp file by using the wladm program or the wladm Ant
task:
By using the wladm program Use the wladm program (provided in the MobileFirst installation directory) to run the enable
extended-authenticity command:
wladm enable extended-authenticity src-wlapp-file device-file > dest-wlapp-file
src-wlapp-file => Original binary app file (.wlapp) device-file =>
Binary mobile app file (.apk, .ipa, or .xap) dest-wlapp-file => Output
binary app file (.wlapp)
After running the wladm , deploy the output file to MobileFirst Server
instance.
By using the wladm Ant task Use the wladm Ant task (provided in the MobileFirst installation directory) to run the
enable-extended-authenticity command:
<enable-extended-authenticity srcwlappfile="original-.wlapp-file"
devicefile="device file(.apk, .ipa, or .xap)"
destwlappfile="output-.wlapp-file"/>
After running the wladm command or Ant task, deploy the output file to MobileFirst Server instance.
