Migrating to DIGIPASS Gateway 5 services
When migrating from DIGIPASS Gateway 4.1 or earlier you probably need to adapt your application websites as well as your mobile applications integrating OneSpan Mobile Security Suite.
If your mobile application uses deprecated services, you should change your application to use the respective services in the current API version provided by DIGIPASS Gateway 5 instead (see DIGIPASS Gateway service mapping (DIGIPASS Gateway 4 vs. 5)).
DIGIPASS Gateway 4 | DIGIPASS Gateway 5 |
---|---|
/activate /licenseActivation |
/rest/v2/provisioning/DSAPPGenerateActivationData |
/addDevice /rest/activation/MdlAddDevice |
/rest/v2/provisioning/MdlAddDevice |
/bind |
/rest/v2/provisioning/DSAPPActivate |
/instanceActivation | /rest/v2/provisioning/DSAPPMdlAddDevice |
/postActivation /signature /rest/activation/MdlActivate |
/rest/v2/provisioning/MdlActivate |
/register /registerOnline |
/rest/v2/provisioning/DSAPPRegister |
/registerOffline | /rest/v2/provisioning/MdlRegister |
/rest/activation/DSAPPSRPGenerateActivationData | /rest/v2/provisioning//DSAPPSRPGenerateActivationData |
/rest/activation/DSAPPSRPGenerateEphemeralKey | /rest/v2/provisioning/DSAPPSRPGenerateEphemeralKey |
/rest/auth/online | /rest/v2/authentication/authUser
See authUser (service). |
/rest/notification/push/sendNotification | /rest/v2/notification/push/sendNotification |
/rest/notification/push/updateNotificationID | /rest/v2/notification/push/updateNotificationID |
/rest/push/cancelLogin | /rest/v2/authentication/push/cancelAuthUser |
/rest/push/retrieveLogin | /rest/v2/authentication/push/getPreparedSecureChallenge |
/rest/push/signLogin | /rest/v2/authentication/push/authUser |
/synchronize | /rest/v2/provisioning/getServerTime |