Weird AnyConnect/iPad issue
colemic
Member Posts: 1,569 ■■■■■■■□□□
Had a very odd situation here, posting in case anyone else ever runs into it.. We use Good for enterprise, and have iPads connect through Anyconnect to access our internal network for an RDP application.
Basically it's this:
User A's UDID: 1234...
User B's UDID: 5678...
When User A connects to AnyConnect, DAP trace shows that User B's UDID (5678 ) is being seen by AnyConnect, as opposed to User A's (1234). User B has no access to AnyConnect, now or in the past.
After a lengthy phone conversation with Good, they thought the issue was with AnyConnect. But I had no idea how B's UDID - which to my understanding is supposed to hard-coded into the device - could appear on someone else's AnyConnect session.
When user B brought his iPad in, sure enough, it was passing the 5678 UDID - so two devices were presenting the same UDID to AnyConnect. We determined that User A in the past had connected via AnyConnect app on his iPad, backed it up to iCloud, and then restored the data to his new iPad, and his old one went to user B. So somehow, the Anyconnect app caches the UDID and doesn't bother to check each session. That is a bit disconcerting, but we were able to confirm by deleting User A's AnyConnect app and resintalling, and it now passes the correct UDID to AnyConnect.
Hopefully this gets fixed soon, it's kind of a big deal (at least to us.)
Basically it's this:
User A's UDID: 1234...
User B's UDID: 5678...
When User A connects to AnyConnect, DAP trace shows that User B's UDID (5678 ) is being seen by AnyConnect, as opposed to User A's (1234). User B has no access to AnyConnect, now or in the past.
After a lengthy phone conversation with Good, they thought the issue was with AnyConnect. But I had no idea how B's UDID - which to my understanding is supposed to hard-coded into the device - could appear on someone else's AnyConnect session.
When user B brought his iPad in, sure enough, it was passing the 5678 UDID - so two devices were presenting the same UDID to AnyConnect. We determined that User A in the past had connected via AnyConnect app on his iPad, backed it up to iCloud, and then restored the data to his new iPad, and his old one went to user B. So somehow, the Anyconnect app caches the UDID and doesn't bother to check each session. That is a bit disconcerting, but we were able to confirm by deleting User A's AnyConnect app and resintalling, and it now passes the correct UDID to AnyConnect.
Hopefully this gets fixed soon, it's kind of a big deal (at least to us.)
Working on: staying alive and staying employed