06-28-2012 11:43 PM
Which device vendor are you using with your Android Devices?
With Asus Tablets I dont get any Pulse Cert Authentication working, no way (but Gingerbread, Android 2.3). JTAC still didnt find a solution either .
07-06-2012 02:28 PM
Is there a specific case number for this issue? I can take a look at it.
The most common issue is the certificate files are not in binary format. If the certificate are in base64, Pulse will fail to read the certificate. Here is a general kb article about how to configure certificate authentication:
07-08-2012 10:34 PM
Its also not working on ICS by the way. Thanks for the KB Article, but I read it mabye 10 times meanwhile and I created the certs as advised.
Yes there is a case and it was just escalated last week. Can I just post the number here?
07-11-2012 04:31 AM - edited 07-11-2012 04:37 AM
Okay I got some Feedback from JTAC now:
There is no solution for this as it is limitation in Pulse version release that is published in market place. We will test this against pulse version 4.0 release code and will let you know the results.
07-11-2012 09:38 AM
Do you have details about this limitation provided by jtac? I'm running on 4.0.4 on a Nexus S 4G so it's not specific to the android version. I've tested certificate authentication on this device with 3.x and 4.x Pulse version and I don't remember running into any limitation.
If you could provide the case number, I can review the existing data.
07-27-2012 03:46 PM
JTAC is correct on this issue. Android for Pulse supports only certificate authentication (through an certificat authentication server). Certificate restrictions on the realm or role are not currently supported.
07-30-2012 12:04 AM
Ok, iOS and Android are different mobile operating systems and iOS have the capability to support both Cert.auth and Cert.check however, Android base os have limitation in this area.