Reputation: 122
I am using the following configuration on my local host to disable direct update, but the direct update shows up randomly.
<securityTests>
<customSecurityTest name="iOSSecurityTest">
<test realm="wl_antiXSRFRealm" step="1"/>
<test realm="wl_authenticityRealm" step="1"/>
<test realm="wl_remoteDisableRealm" step="1"/>
<test mode="disabled" realm="wl_directUpdateRealm" step="1"/>
<test isInternalUserID="true" realm="wl_anonymousUserRealm" step="1"/>
<test isInternalDeviceID="true" realm="wl_deviceNoProvisioningRealm" step="2"/>
</customSecurityTest>
Upvotes: 0
Views: 565
Reputation: 44516
I would try two things:
wl_directUpdateRealm
test altogether from the security testwl.realm.expiration.directUpdate
in worklight.properties, as it is this value that dictates when will the direct update check take place.Either way it sounds like you may want to open a PMR to have it checked by the development team why "disable" is not working.
Note that if this is in an external server you must re-deploy the .war file if making any changes to any file under the "server" folder.
Upvotes: 0