(INTERNAL) Configure Minimum and Recommended Version for SecureAuth (Arculix) Mobile App

Summary

This article describes how to configure minimum and recommended version requirements for the Arculix Mobile App within the Active Admin dashboard of a Workforce SaaS tenant.

By enforcing a minimum version, administrators can ensure all users are running a consistent, up-to-date version of the mobile app. Additionally, the recommended version setting allows organizations to encourage upgrades without blocking access.

These features are particularly useful when deploying new functionality—such as Passkey support—that requires users to upgrade their app before use.

Description

The Active Admin dashboard allows organizations to define both:

• Minimum supported version (min_version)
• Recommended version (recommended_version)

for Android and iOS applications.

Minimum Version

• Enforces a hard requirement
• Users on lower versions:
  • Cannot proceed
  • Must update the app

Recommended Version

• Enforces a soft requirement
• Users on lower versions:
  • See an update prompt
  • Can dismiss and continue

This helps administrators:

• Maintain uniformity across users’ app versions
• Ensure availability of new features and security improvements
• Reduce compatibility issues between app versions and backend services
• Gradually roll out updates without disrupting users

How to Configure Minimum Version for Mobile App

• Log in to the Arculix Admin Dashboard that is linked to your Workforce SaaS tenant.

  EU Environment URL: https://workforce.services.eu.connect.secureauth.com/

• Navigate to Active Admin, then select Devices → Device Applications.

• From the list of available mobile applications, click Edit next to the application for which you want to enforce the minimum version.

• In the General tab, scroll down to the Config section.

• Add the following configuration with the desired version numbers for both iOS and Android platforms.

• Click Update Device Application to save the changes.

{
  "min_version": {
    "ios": "200",
    "android": "4.1.1"
  },
  "recommended_version": {
    "ios": "210",
    "android": "4.2.0"
  }
}

Expected Behavior

Minimum Version

• Users with app versions below min_version:
  • Are blocked from accessing the app
  • Must update before proceeding

Recommended Version

• Users with app versions below recommended_version:
  • Receive an update notification
  • Can continue without updating

Important Notes

• The configuration applies per application entry under Device Applications
• recommended_version must be greater than or equal to min_version for each platform
• If recommended_version is not defined, only the minimum version enforcement will apply
• Always define both iOS and Android values to avoid inconsistent behavior

Best Practices

• Use min_version for:
  • Security fixes
  • Critical feature dependencies
• Use recommended_version for:
  • Gradual rollout of new features
  • Encouraging adoption without disruption
• Align version values with your mobile release cycles

Additional Notes

• This configuration is especially relevant when enabling features such as:
  • Passkeys
  • Enhanced mobile security controls
• This use case also applies to JPMC environments