Provisioning for Android
Because of security considerations, the Android agent must be downloaded from the Android marketplace site and cannot be provisioned from ISE. Cisco uploads a release candidate version of the wizard into the Android marketplace through the Cisco Android marketplace publisher account.
This is the Android provisioning process:
- Cisco uses the Software Development Kit (SDK) in order to create the Android package with a .apk extension.
- Cisco uploads a package into the Android marketplace.
- The user configures the policy in client provisioning with the appropriate parameters.
- After registration of the device, the end user is redirected to the client provisioning service when dot1x authentication fails.
- The provisioning portal page provides a button that redirects user to the Android marketplace portal where they can download the SPW.
- The Cisco SPW is launched and performs provisioning of the supplicant:
- SPW discovers the ISE and downloads the profile from ISE.
- SPW creates a cert/key pair for EAP-TLS.
- SPW makes a Simple Certificate Enrollment Protocol (SCEP) proxy request call to ISE and gets the certificate.
- SPW applies the wireless profiles.
- SPW triggers re-authentication if the profiles are applied successfully.
- SPW exits.
https://play.google.com/store/apps/details?id=com.cisco.cpm.spw.android.wifisupplicant&hl=en