Hi,
A new method has been added in the interface UserHandler to enable/disable a user which is setEnabled(String userName, boolean enabled, boolean broadcast), in case it cannot be supported by the implementation, an UnsupportedOperationException can be thrown.
For each find methods in the interface UserHandler, we have the corresponding method with a new parameter which is enabledOnly, the old methods call the new ones with enabledOnly set to true.
Some old methods such as saveUser and authenticate can now throw a new exception called DisabledUserException in case we try to interact with a disabled user account.
The TCK has been reviewed to cover this new feature, I also added more unit tests to make sure that all implementations behave the same way.
Finally, to allow the UI to be able to know which error occurred during the authentication, I added a new method in the interface Authenticator which is getLastExceptionOnValidateUser()
In this branch I also upgraded our internal implementations (hibernate and ldap) and tested them successfully on Oracle 11G R2, MySQL 5.5, PGSQL 9.1, DB2 9.7.4, MS SQL 2008 R2, H2, HSQLDB, Sybase 15.7 for hibernate and Active Directory 2012, Oracle Directory Server 11g, open LDAP 2.4, openDS 1.2, 2.0 and 2.2.1 and ApacheDS 1.5.7 for ldap
I need now to write some doc about this new feature.
@IDM Team you should have everything you need to upgrade IDM on your side.
@Gatein Team: you should have everything you need to update the UI consequently.
If you have any questions and/or remarks, feel free to share.
BR,
--
Nicolas Filotto
Project Leader JCR
eXo Platform SAS
nfilotto@exoplatform.com