Bug: URL Enrollment From an iPad Registers as a Mac and Is Not Offered as an MFA Method

Version Affected: All
Bug Number: EE-3624
Bug Status: Open - Workaround Only
Fixed in Version(s): Not yet fixed as of this article's last review — check current release notes for status.

 

Overview

When a user enrolls an iPad in a URL Enrollment realm using the SecureAuth Authenticate Mobile application, the device is registered as a Passcode application device named Mac instead of Authenticate Mobile, and is not offered as a multi-factor authentication (MFA) option during login in Self-Service or Helpdesk realms.

 

Cause

The iPad's Safari browser identifies itself to the realm as a desktop browser rather than a mobile browser. Because URL Enrollment decides which application to enroll based on the browser's reported device type, the realm treats the iPad as a desktop device and enrolls it as a Passcode application (SecureAuth's desktop OTP client) instead of Authenticate Mobile.

 

Resolution / Workaround

Use the following workaround:

1. Clone the existing URL Enrollment realm.
2. Configure the cloned realm as a QR Code enrollment realm instead of URL Enrollment.
3. Open the QR Code enrollment realm on a different device (not the iPad). On the iPad, open the Authenticate Mobile app and use its Scan QR Code option to scan the code and complete enrollment.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.