CODEWITHSUNDEEP
upgradeibm-mobilefirstmobilefirst-adapters
Olimpiu Olar
Olimpiu Olar

Reputation: 43

Production MobileFirst 7 Server upgrade from Worklight 6.2, Adapter call not working

We have a MobileFirst application that worked with Worklight 6.2 server - production also. We are using a http adapter: <connectionPolicy xsi:type="http:HTTPConnectionPolicyType">

Currently we are changing the production server to 7.0.0. On Development Server we could test our application and all the functionalities were OK. We'we created the .war with the production server on build configuration and uploaded together with the android .wlapp . Now we receive 404 when the application tries to call any adapter function on production server. invokeProcedure onFailure returns UNEXPECTED_ERROR. This is with:

We have no security enabled in the application. Is there something that must be enabled on Server in order to allow old type adapters call?
When we've tested with upgraded MobileFirst Development Studio 7.0.0.00.20150430 as development platform - same server version, and we got same 404 (Context not found), but there tries to connect with authorization/v1/clients/instance instead of /apps/services/api/XXXXX/android/query

Should a Server upgrade solve this problem? We've noticed that there are updates available.

The Server is on a https connection, but was same on WL 6.2.

Upvotes: 1

Views: 334

Answers (1)

Idan Adar
Idan Adar

Reputation: 44516

By the description in the comments and the supplied messages.log, it is clear that you are attempting to use Application Authenticity Protection.

This feature worked in a certain way in v6.2 and it works in a different way in v6.3 and above.
From the comments it appears you are only adding the publickSigningKey - this is no longer enough.

See the updated Application Authenticity Protection tutorial for steps to follow: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/authentication-security/application-authenticity-protection/

General steps to follow:

  1. Setup authenticationConfig.xml with the security test
  2. Add the security test to the environment node in application-descriptor.xml
  3. Add the publicSigningKey to the <publicSigningKey> element
  4. Add the application package name <packageName> element

I believe you are missing step 4.
Note that you also able to now enable the Extended Authenticity mode; follow the instructions in the tutorial.

Note about step 3: obviously the same keystore used to generate the publicSigningKey must be used when you export the signed .apk file... otherwise there will be a mismatch and the authenticity challenge will fail.

In your authenticationConfig.xml, make sure you have the securityTest available (= not commented out like in the file you've supplied in the comments below.

In your application-descriptor.xml, you are missing the securityTest attribute in the Android environment element: <android version="0.9.9"> change to <android version="0.9.9" securityTest="customTests">

Upvotes: 1

Related Questions