Silverpeas/Silverpeas-Core — pull request #205 by mmoqui (2012-07-25 18:37:32+00:00)
Title: Rest authent

Feature #3583 in Redmine
Now, when a client of a REST-based WEB resources authenticates itself with the header Authorization in the HTTP request, a session is opened in Silverpeas, managed by the SessionManagement implementation (currently the SessionManager single object), and the key of the opened session is sent back to the client within the HTTP response. So, the client has just to set the header X-Silverpeas-Session into each of its HTTP request to be authorized to access a WEB resource without to reauthenticate itself.

The SessionManager was slightly modified to take into account of this new process ; the sessions in the REST-based WEB services are represented by a com.silverpeas.session.SessionInfo instances whereas the com.stratelia.silverpeas.peasCore.SessionInfo becomes the com.stratelia.silverpeas.peasCore.HTTPSessionInfo and it is mainly used to represent a classical WEB user session (it wraps the HttpSession instance).