Make it easier to disable BruteForceLocker (#1345)

Activities

wojciech.kapcia@tigase.net opened 2 years ago

Currently, to disable BruteForceLocker one has to disable it in the configuration and for each VHost, which is somewhat inconvenient. It should be possible to simply set disable BruteForceLockerBean but currently this could lead to NPEs.

All injections of BruteForceLockerBean should be configured with nullAllowed = true and proper checks should be added.

Add information to the documentation as well.

wojciech.kapcia@tigase.net commented 2 years ago

Change is now implemented. BruteForceLocker bean has been pulled up and encapsulated in AbstractAuthPreprocessor. Sasl plugins were refactored a bit to SaslAuthAbstract to reduce code duplication.

wojciech.kapcia@tigase.net batch edited 6 months ago

Name	Previous Value	Current Value
Iterations	empty	tigase-server-8.4.0

Type	Bug
Priority	Normal
Assignee	wojciech.kapcia@tigase.net
Version	tigase-server-8.4.0

Iterations

tigase-server-8.4.0 Closed

Customers/carnow-inc#112 You are not authorized to access this issue
Customers/carnow-inc#139 You are not authorized to access this issue

Issue Votes (0)

Watchers (2)

Reference

tigase/_server/server-core#1345