I'm having an issue onboarding android devices, all steps works fine but after the onboarding when the android device tries to authenticate with TLS always getting an error in access tracker showing client error uknonw_ca, when i check the settings on the wireless on the android device I cannot see a CA defined and when i click on that no CA showing, in the onboarding steps it shows it installed RC but doesn't seem to be recognized by the Android device.
I have made sure that the correct certificate is selected as trusted on the onboarding steps for Android, but 1 thing is that in the manual it is mentioned:
6. In the Android Trust area, use the Trusted Certificate drop-down list to select a certificate the device should trust.Android supports only a single trusted certificate; this must be the root CA that issued the authentication server’scertificate. Be aware that if None is selected, 802.1x authentication might not work.
But I can see the Server Certificate not the CA !! I also tried Creating new Root Certificates and changed the names several times still the same result, the SSID is simple "JCAccess" since i faced an issue with the SSID name before and now using simple ones.
Did anybody face this issue before ?
Please help, and if possible to let me know if there is a way to downgrade from 6.1 to 6.0.2 so I can avoid this as I have tested with 6.0.2 and no issues like this.
You should probably not be configuring custom trust settings for Android.
Use the setting "Automatically configure trust settings (recomended)" on the Onboard » Configuration Profiles » Network Settings » Trust tab. This should work correctly.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.