title: "Re-enabling" App Authenticity in Mobilefirst 8.0 not working
body: <p>During App Authenticity testing in MobileFirst 8.0, I found a strange behavior in switching between enable and disable of App Authenticity setting on Console, using an (Android) app's debug package and release package:</p>
  
  <ul>
  <li><p>Followed the instruction of signing the app (release package) with mfp-app-authenticity-tool.jar tool, registered .authenticity_data file via Console, and set Security-Check Configurations of the app to use appAuthenticity setting with Expiration Period value.</p></li>
  <li><p>(For initial connection) After installing the release version of the app on a device, the app successfully connects to MFF Server and calls an adapter.</p></li>
  <li><p>(After removing the release version of the app from the same device) Installed debug version of the app on the device, and the app fails to connect to MFF Server, as expected.</p></li>
  <li><p>Disabled App Authenticity by deleting Authenticity File on Console, the debug version of the app on the device successfully connects to MFF Server and calls an adapter.</p></li>
  <li><p>"Re-enabled" App Authenticity with same instructions as the first step, but <strong>the debug version of the app still can connect to MFF Server and calls an adapter</strong>. I understand that there's Maximum Token-Expiration Period and Expiration Period setting, but I set both value to 60 seconds for just testing. (Reinstalling the debug version of the app and testing the action without changing on Server gives an expected behavior - i.e. not able to connect.)</p></li>
  </ul>
  
  <p>I'm wondering if this is normal behavior of enabling / disabling App Authenticity setting in real-time on Console.. and if the feature is designed for just one set of actions of Enable -> Disable only.</p>
  
  <p>Any thought?</p>
  
  <p>Thanks!</p>