MDM Authentication and PWPolicy lockouts

[Luke-From-IT]

Referencing this as it is directly related

#183

I am experiencing the issue above, but we are using --auth-jamf-client and --auth-jamf-secret.

As far as I can tell, the bug fix to the solution above was to get super to stop running once it detects that the authentication has failed.

I can restart the super process to attempt to get super to work again, but this further causes an incorrect password attempt on the device and increments the failedLoginCount key by 1 when running this command; further tries of this will repeat until we reach the number set in pwpolicy for Maximum Number of Failed Attempts, and locking the account.

dscl . -read /Users/$USERNAME | grep -A1 failedLoginCount

        <key>failedLoginCount</key>
        <integer>2</integer>

Is there a solution to make Super restart the workflow when using the auth-jamf-client options without causing further lockouts?

[tranziq]

i am having the same issue.

[Macjutsu]

Ineed this is likley related and stems from an issue with Apple breaking the softwareupdate download function. I'm working on a solution in super v5.1, but it requires a significant reachitecting of the internals of the super workflow.