d to allow these.
Regards,
Inosh
On Wed, Jan 31, 2018 at 3:00 PM, Madhawa Perera <madha...@wso2.com> wrote:
> [Added InoshP]
>
> -- Forwarded message --
> From: Madhawa Perera <madha...@wso2.com>
> Date: Wed, Jan 31, 2018 at 2:53 PM
> Subject: Re: [Architecture
Hi MadhawaS,
+1
It was take from the iOS protocol. Since we cannot change the protocol
which says "Specifies whether the user must enter alphabetic characters
("abcd"), or if numbers are sufficient.", My suggestion is we should change
the UI with that value.
Regards,
Inosh
On Wed, Jan 31, 2018
Hi Inosh at el,
+1 for the idea so the users have the same experience when using/enforcing
policies to there managed mobile devices. Can't we follow the same approach
in windows as well, so we can expose the same experience all whole EMM use
case? WDYT?
Thanks and Best Regards,
On Wed, Jan 31,
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
Hi Inosh,
On Tue, Jan 30, 2018 at 3:33 PM, Inosh Perera 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.
>
>
Hi Inosh,
Please find inline comments.
> 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
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