android-for-work

SSl hand-shaking getting failed on enterprise Android but working good with ordinary devices

蹲街弑〆低调 提交于 2019-12-02 06:40:45
问题 I am facing the issue in making SSL connection with the enterprise devices. When I run my application on normal android devices the SSL hand-shaking get successful. I don't know why this is happening the code should work with both the devices. Here is my code for choosing a certificate and extracting alias private and certificate chain : public void userAliasCertificateSelection() { boolean isGranted = appPreferences.getPrefrenceBoolean("mycertificate"); if (!isGranted) { //Get cert and

SSl hand-shaking getting failed on enterprise Android but working good with ordinary devices

China☆狼群 提交于 2019-12-02 04:24:51
I am facing the issue in making SSL connection with the enterprise devices. When I run my application on normal android devices the SSL hand-shaking get successful. I don't know why this is happening the code should work with both the devices. Here is my code for choosing a certificate and extracting alias private and certificate chain : public void userAliasCertificateSelection() { boolean isGranted = appPreferences.getPrefrenceBoolean("mycertificate"); if (!isGranted) { //Get cert and private key from internal android store KeyChain.choosePrivateKeyAlias(this, new KeyChainAliasCallback() {

How to use Managed Configurations in an app that may not have a Managed Configurations Provider?

不羁的心 提交于 2019-12-02 00:54:13
I am developing an app that will work in 2 different Android environments (consumer & corporate markets). Lets say it is a texting app with a dozen configuration parameters to manage. The first environment is a standard Android device that has no Android Enterprise (AfW) features enabled. So there is no EMM (MDM) to supply an Android Agent/Client app to be a device/profile owner implementing a Managed Configurations Provider. The second environment is within a corporation. An EMM (MDM) is used to manage all their corporate owned devices. The EMM is either a device or profile owner. They are