Hi Rasika, Please find the possible combinations and the minimum password needed bellow, isSimple isAlphanumeric isComplex Minimum sufficient password y n n 1234 y y n 1234a y y y 1234a# n y y 1234a# n n y 1234# y n y 1234# n y n 1234#h n n n 1234# Regards, Inosh
On Wed, Jan 31, 2018 at 11:51 AM, Charitha Goonetilleke <[email protected]> wrote: > Hi Inosh, > > On Tue, Jan 30, 2018 at 3:33 PM, Inosh Perera <[email protected]> wrote: > >> Hi all, >> >> Currently the passcode policy of IoT server for Android and iOS platforms >> seems to have followed 2 different approaches and this inconsistency can >> lead to confusion for an EMM administrator. >> >> *Following are the inconsistencies,* >> In iOS protocol, allow simple passcode means that the user is free to >> enter just a pin or any passcode. However with Android currently, it must >> be a alphanumeric value only. >> Also in iOS disallow simple is equivalent to having at least one complex >> characters regardless of the alphanumeric check. When alphanumeric is not >> required and complex characters are set to 1, the user should be able to >> add a password like "1234$" as the passcode and currently Android policy >> does not support this behaviour and it ask for a minimum one alphabetic >> character regardless of the state of alphanumeric checkbox. Therefore to >> get rid of these inconsistencies, I suggest we should make the Android >> passcode policy work similar to iOS. >> >> *Solution* >> Therefore, as per iOS protocol, following would be the standard of the >> passcode policy, >> allowSimple - If a simple passcode containing just numbers or just >> letters or combination is allowed. Setting this to "no" mean, a complex >> passcode is required and of minimum of 1 complex character together with >> numbers or alphabets characters. >> minComplexChars - A complex character is a character other than an >> alphanumeric value. Setting min complex chars restriction will not mean >> that an alphabetic character is required. >> requireAlphanumeric - Whether alphabetic characters are required or is it >> enough to have numbers only. >> > > +1, By doing so we can have same experience for pass code policy. Anyway > with current design, we have clear separation with Android and iOS > policies. So still we might have to keep those two policy wizards. > > >> >> Regards, >> Inosh >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > Thanks & regards, > /charithag > > -- > *Charitha Goonetilleke* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 77 751 3669 <%2B94777513669> > Twitter:@CharithaWs <https://twitter.com/CharithaWs>, fb: charithag > <https://www.facebook.com/charithag>, linkedin: charithag > <http://www.linkedin.com/in/charithag> > > <http://wso2.com/signature> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Inosh Perera Senior Software Engineer, WSO2 Inc. Tel: 077813 7285, 0785293686
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
