fixing bug #5135
authentication values are no more removed from session
fixing bug #5130
upgrading JQuery from 1.10.1 to 1.10.2
fixing bug #5130
bug #4783 : A new method is added to the SilverpeasContent interface: canBeAccessed(). This method is to verify a specified user has enough rights to access the content. Each concrete content must implement their way to verify the access right of a user by using the correct access controllers.
The comment notification service uses now this new method to verify a user can be recipient of the notification. In order to be notified, a user must have the privileges to access the commented content.
fixing bug #5154
using UserNotificationBuilder to separate notification stuff from PDC subscription business
bug #5154 : incorrect sender for pdc notification
- taking the opportunity to fix a little problem around the footer of the mail sent by delayed notification mechanism
- refactoring the inheritance of created PDC user notification classes and renaming them in order to be homogeneous with the existing ones
bug #5107 :  Add a new parameter server.mixed to permit a site to be mixed with a secured authentication and a site navigation in clear. By default, this parameter is false and we don't recommend to setup a site in a mixed mode as it is a flaw in the security
fixing bug #5094
catching error which blocks indexer thread
adding some logs and adjusting some logs level
bug #5154 : incorrect sender for pdc notification
- fixing unit test failures
security #token :  The subscription panel didn't work because it used the old code on the user profiles. To fix this error, the panel uses now the new user profile service based upon AngularJS and it is updated to take in charge the use of promises to chain asynchronous computations
security #token :  Adding the library CSRFGuard to manage synchronizer tokens
security #token :  Refine the session opening in Silvepeas when authenticating a use. The refinement is based upon the assumption that in JEE, each incoming request is associated with a session. When a user logon to Silverpeas, an HTTP session is already existing and this session is then reused as the user specific session once the authentication succeed and it is the set up with some attributes (main controller, ...). If the user had already an opened session with Silverpeas during the autentication process, then this session is no more closed and it is reused as such
security #token :  Pass to version 1.2.3 of AngularJS (previously 1.2.2). Fix an error with the user panel when the selection is only on users (discovered when selecting a validator for a publication in creation). Fix also an error with the comment JQuery-based plugin that used the old silverpeas-profile js; it uses now the one based upon angularjs.
security #token :  Remove the use of the OWASP CSRFGuard library as it doesn't work well and there is no answer to our fix. So we are starting to implement our own security token (synchronizer token) by inspiring ourself on the way it is implemented by CSRFGuard. Before starting to implement our own security token solution, the existing token API in Silverpeas is refined in order to accept other than persistent tokens. The persistent tokens are generated for some types of resources in Silverpeas in order to access them or to access some contents in Silverpeas authorized by the token; currently, such tokens are only used for users to access Silverpeas without passing by any required authentication mechanism. The refinement of this API is now done.