Impact of Changing Bundle ID on Mobile SDK Application Upgrades.

Products

• CA Strong Authentication
• Advanced Authentication Mainframe
• CA Advanced Authentication
• CA Advanced Authentication - Risk Authentication (RiskMinder / RiskFort)
• CA Secure Cloud SaaS - Advanced Authentication
• CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort)

Issue/Introduction

Need to understand the impact of changing the IOS Bundled ID or Android package Name during an application upgrade, and whether any workaround exists to prevent mandatory user re-enrollment.

Environment

Product: Symantec  Advanced Authentication

Component: Mobile Authenticator SDK (iOS and Android)

Resolution

In general, organization that use the Mobile SDK and develop their own applications should retain the same IOS Bundle ID and Android Package Name when upgrading the application. With this approach only the application version is updated (for example: from version 2.11 to 2.12) through the respective app store. This preserves existing user accounts and prevents the need for user re-enrollment.

• Account Retention: Maintaining the same Bundle ID allows the operating system to treat the new version as an update to the existing app, preserving the secure storage/database used by the SDK.
• Re-enrollment Trigger: Changing the Bundle ID causes the mobile OS to treat the update as a completely different application. This results in the loss of access to the previous app's data, effectively forcing all users to re-enroll.
• Standard Practice: This approach aligns with the standard release process used by Broadcom for the CA Mobile Authenticator app in public App Stores.

Additional Information

If a business requirement necessitates changing the Bundle ID, please engage the Professional Services team. They can provide architectural guidance or evaluate specific migration use cases to determine if a custom transition path is feasible.