feature #4148 :  Rename some classes to a more appropriate name according to their responsibility. Remove the deprecated and no more used method LoginPasswordAuthentication#getAllDomains() and replace it by the getListDomains()
feature #4148 :  Introduce the AuthenticationCredential class to gathers all the data that can be used in a user authentication. Change the signature of some methods used in the authentication as consequency. Refactor the code that perform the authentication, the password change and reset in the AuthenticationServer class in order to to facilitate its reading and to optimize a little its code. Do similar approach with the Authentication class hierarchy.
feature #4148 :  Change the signature of the changePassword by replacing the parameters login, oldPassword and domainId by a single object AuthenticationCredential
feature #4148 :  Refactor the encryption of passwords: now each encryption methods for passwords are represented by an implementation of the PasswordEncryption interface. A factory of password encryption is provided to wrap the concrete encryption in use in Silverpeas. Now, only one cryptographic method is used at once on passwords; there are no more several ways to encrypt a password: this simplify greatly the code. To take into account of an algorithm transition period, the previous encryption method is retrieved from the password digest in order to authenticate the user until its password is changed with the new cryptographic algorithm.
feature #4148 :  Move the code related to the authentication to the package org.silverpeas.authentication. Only old code seaming no more used by anymore stays in place
feature #4148 :  Merge branch 'master' of github.com:Silverpeas/Silverpeas-Core into feature-4148
feature #4148 :  Now the default cryptographic function to encrypt the user passwords is the Unix-based SHA-512 variation. So, the size of the varchar type in the database to store the user passwords have to be increased up to 123 characters (the maximum size of the digest computed by the new algorithm); the SQL migration of busCore is then updated in three ways: in first, SQL instructions are provided to set the varchar size at 123 characters for the password field; in second, the password of the administrator is now encrypted with the new algorithm (see the change in the Silverpeas-Setup project); and in last, all of the customer's SQL domains are browsed in order to change the password type in the 'user' table of these domains
feature #4148 :  Merge branch 'master' of github.com:Silverpeas/Silverpeas-Core into feature-4148
feature #4148 :  When creating a SQL domain, the type of the password field in the user table is now a varchar(123)
feature #4148 :  Fix the merge conflict with the work done by Yocha on some parts of the code I have worked on
feature #4148 :  Be caution with some guidelines in Java: usually, a check method arises an exception when the check fails and doesn't return a boolean. When validating an object, the validation process either throws an exception (like a check method) or in a better way returns the validation errors (empty if all is ok). (Methods that returns a boolean should be prefixed by either is or has term.)
Merge branch 'feature-4148' of https://github.com/mmoqui/Silverpeas-Core into mmo-feature4148