Hi, Jake.
I think it's because Gluu itself is rarely being used as authenticator, most of the times it relies on some backend for that, which is already should have such protection as usually it belongs to pre-existing infrastracture (for example, AD's LDAP Provider has this feature)
But if you really need to use Gluu's internal LDAP directory for authentication, you can enable account lockout in OpenDJ:
[http://opendj.forgerock.org/doc/admin-guide/index/chap-account-lockout.html](http://opendj.forgerock.org/doc/admin-guide/index/chap-account-lockout.html)
Regards,
Alex.