Re: [Architecture] [IoT][Android] Making Android passcode policy to be consistent with iOS

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

Re: [Architecture] [RRT] XACML based scope validator (during OAuth2 token validation)

Hi Senthalan, On Tue, Jan 30, 2018 at 9:33 AM, Senthalan Kanagalingam wrote: > Hi all, > > We had a discussion regarding the state of this project. Please find the > meeting notes below, > > Participants: Dimuthu, Ruwan, Darshana, Nadun, Pamoda, Biruntha > >- Have

Re: [Architecture] [IoT][Android] Making Android passcode policy to be consistent with iOS

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. > >

Re: [Architecture] [IoT][Android] Making Android passcode policy to be consistent with iOS

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

Re: [Architecture] Password Rotation Policy Authenticator

Hi All, The notes from the review we had on the "password rotation policy" progress are as follows. Participants: DimuthuL, RuwanA, Darshana, Pamoda, Senthalan 1. Consider the following when finding *unique* password change events 1. Tenant ID 2. Username 3. Domain 2.

[Architecture] [IoT][Android] Making Android passcode policy to be consistent with iOS

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

Re: [Architecture] [RRT] XACML based scope validator (during OAuth2 token validation)

Hi all, We had a discussion regarding the state of this project. Please find the meeting notes below, Participants: Dimuthu, Ruwan, Darshana, Nadun, Pamoda, Biruntha - Have multiple checkboxes in OAuth UI for all scope validators. Then users can pick on their wish. - When calling the