Backward compatibility

Article summary

Did you find this summary helpful?

Thank you for your feedback

<BackwardCompatibility>
<Challenge minLength="1" maxLength="16" />
<DataFields>
<DataField minLength="1" maxLength="16" />
<DataField minLength="0" maxLength="16" />
<DataField minLength="0" maxLength="16" />
</DataFields>
<ActivationResponse serverTime="serverTime" xfad="xfad" retCode="retCode" message="message" />
<SynchronizeTimeResponse serverTime="serverTime" />
<AdvancedActivationV1 enabled="false" />
<ChecksumV1 enabled="false" />
</BackwardCompatibility>

BackwardCompatibility: This element is used to maintain backward-compatibility with legacy server integrations or authenticators.

BackwardCompatibility > Challenge: This element defines the challenge length for updated Mobile Authenticator Studio authenticators.
BackwardCompatibility > DataField: This element defines the signed data field length for updated Mobile Authenticator Studio authenticators.
BackwardCompatibility > ActivationResponse and BackwardCompatibility > SynchronizeTimeResponse: If the server response is in text format rather than XML (as is the case with Mobile Authenticator Studio versions prior to 3.5), these elements are used to define the name of the parameters in the text response.
BackwardCompatibility > AdvancedActivationV1: This element configures Mobile Authenticator Studio to be used with the Digipass Software Advanced Provisioning Protocol (DSAPP) server library using encryptActivationData instead of encryptActivationDataV2.

BackwardCompatibility > ChecksumV1: This element configures Mobile Authenticator Studio to be used with the DSAPP server library using generateSharedData instead of generateSharedDataV2.

Was this article helpful?