t designed to allow these.
Regards,
Inosh
On Wed, Jan 31, 2018 at 3:00 PM, Madhawa Perera wrote:
> [Added InoshP]
>
> -- Forwarded message --
> From: Madhawa Perera
> Date: Wed, Jan 31, 2018 at 2:53 PM
> Subject: Re: [Architecture] [IoT][Android] Making Android passc
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,
This is indeed a good approach to have a consistency in passcode policy
regardless of the platform. Even though we maintain two separate policy
wizards this will help to minimize the confusion of MDM administrators when
pushing the same policy to both iOS and Android devices.
Anyhow, I
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, 2
Hi Inosh,
requireAlphanumeric - Whether alphabetic characters are required or is it
> enough to have numbers only.
>
AFAIK, alphanumeric characters include both alphabetic characters and
numbers [1]. So if we use 'requireAlphanumeric' option to force using
alphabetic characters, wouldn't it be co
Hi Charitha,
+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.
Since policies are platform specific, even if the passcode policy's
behaviour
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
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.
>
> *Following are the i
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 is
10 matches
Mail list logo
