0

Our application have been running in production for about 6 months now. Suddenly we experience weird errors in our mobile app. We found out from the logs that there was a sudden change in the behavior of the response thrown by MFP.

Our MFP adapter interfaces to the app on one side, and connects to REST web services in the back end side.

Before, the behavior was like the one below. isSuccessful returns "true" even if HTTP status code returned from the REST web service was any other http code besides 200.

{  
   "statusCode":401,   
   "errors":[  

   ],
   "isSuccessful":true,
}

Now, if the status code is not 200, isSuccessful is showing false. We did not change anything in the MFP adapter code nor made any changes in MFP as well. This causes our application to behave in a different way than before. 

{  
   "statusCode":401,   
   "errors":[  

   ],
   "isSuccessful":false,
}

Does anyone know the reason for this sudden change in behavior? we want to return the behavior as how it was before.

Hingle McJingleberry
  • 541
  • 4
  • 26

1 Answers1

0

Mobile App will receive an 401 HTTP Status code whenever the user invokes an adapter endpoint with invalid Access token.

Check whether you have protected your Adapter Endpoint Custom OAuth Scope with any Security Check in Mobilefirst Operations Console.

If not, MFP SDK will handle this error and obtain's a fresh access token for default OAuth Scope and returns the adapter response.

Vittal Pai
  • 3,317
  • 25
  • 36