-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pwpolicy_account_lockout_enforce issues with Sonoma #311
Comments
So I'm not able to reproduce this. I created a baseline file with just the 1 rule. And it appears when I run with --check it spits it out correctly. Are you setting an ODV value? Can you copy/paste your custom rule? |
|
Can you provide the output of |
|
Your password policy has You can clear them by |
Thanks @brodjieski and @robertgendler! That resolved my issue. Any idea why it populated twice? |
When password policies are applied with a profile, they get written to pwpolicy, however when you remove a profile, it doesn't clean itself up. So depending on how you applied or removed profiles, old policies may still be in the mix. |
Closing, since it's resolved. |
Discussed in #310
Originally posted by danieldotweinert September 28, 2023
Currently having this issue with the Sonoma compliance script...as you can see the output show it as 'yes' but includes a line break and extra yes which is causing the rule to fail and make the device non compliant. Any ideas?
Thu Sep 28 19:58:14 UTC 2023 pwpolicy_account_lockout_enforce failed (Result: yes
yes, Expected: {string: yes})
The text was updated successfully, but these errors were encountered: