Password Requirements policy

This will be in your configuration profiles under password profiles. I think it will be the "allow simple value" checkbox.

Hello Ryan,

As far as I know that is part of the "security / Require Passcode" setting and controlled by "Require Complex Passcode"

Kind regards,
Raymar

Hi,

i noticed the same while the settings are correct Mac OS is still asking the question;

I thought this was because we had require alphanumeric enable, but now I am guessing that it's on the client side. While we were moving to local passwords and I was doing testing we never saw two consecutive, or three sequential characters. Then Apple released an OS updated and we went live with local password on the same day. Since it's more secure and only a few users were "upset" I never dug into it. However, I did just take a quick look at it, but because the Jamf profiles are signed it's not super easy to "read"... I didn't see any keys that explain "Not have two consecutive, or three sequential characters" and I didn't have Require Complex Passcode/require alphanumeric enabled.

Best guess is that it's hidden on the client side.

C

so any idea how to get this fixed? because pass phrases will have consecutive or sequential characters? it seems that the password policy is not completely applied as in jamf set.

UPDATE

so it seems that the policy is not wiped before changing, by manually wiping and replying the policy it worked;

sudo pwpolicy -clearaccountpolicies

could you please extend the number of minimum required characters within jamf?

Has this happened to anyone recently?
We are not enforcing a pwd policy thru jamf pro or jamf connect. We are only enforcing thru Okta (our IdP) and it does not have this rule, but when the end user went to sync okta pwd with local macbook, they received this notification.

New password must NOT:

• have two consecutive characters

• have three sequential characters

I encountered this issue with another MDM, and raised this issue with their support team. They ended up apparently identifying this as a MacOS bug, and said they have filed a bug report with Apple.