Currently we don't support the passwordAttemptThreshold (it defaults to 5), but you can determine when accounts automatically unlock (or if they do). Log in as host, and go to host->host settings. Expand out other settings-> and you can set a value for  “Auto-unlock accounts after (minutes)”. After an account is locked out due to unsuccessful login attempts, it can be automatically unlocked with a successful authentication after a certain period of time has elapsed. Enter the number of minutes to wait until the account can be automatically unlocked. Enter "0" to disable the auto-unlock feature. The default is 10, it is recommended that you either set it to a large value or disable the autounlock function by setting it to 0. If you set it to zero, then the only way accounts can be unlocked is if a portal admin or superuser unlocks them via the “User Accounts” menu.

Cathal

There is no support in the current version for changing max attempts (it's set to 5), but the user is notified of lockout. The issue comes with our integration with the memberrole, and you're correct that this is being extensively reworked for the next release (Charles documents many of the changes on his blog. ) I haven't checked to see if maxattempt support has been added yet (it may be), but I haven't noticed it on the sourcecontrol logs.

Cathal