Thank you for your feedback.
Let me elaborate on our specific case. We are going to build two web sites based on an Alfresco 3.4 Enterprise CM repository. We are considering using the Spring/Surf framework, and also using the Web Quick Start as a starting point.
Our sites will run as external applications inside an IFrame Portlet which is deployed on a jbossportal application.
The authentication will be managed by calling a Single Sign On Web Service running inside the jboss application.
Once authenticated, the users will navigate the aformentioned Spring/Surf sites. Based on a user profile associated to their login, they will be granted access to part of the contents and denied access to others. For example, a user could be able to see all the news titles, but should be able to expand and read only the ones that he is enabled to (we will eventually provide paid content).
So apart from the authentication, that will be managed by an external SSO, we will also have to implement some profiling. It seems natural to me to use the profiling mechanism built into the alfresco repository. So what we would like to do is to define our user, roles and credentials regarding access to content folders/categories in Alfresco, and to implement a Surf application that retrieves the content to be presented to the user based on this configuration.
We have already seen that the Javascript API for accessing content in the repository, provided by Alfresco, allows the use of a token identifying a user session, and thus allowing the transparent leverage of the authentication/profiling layer built-into the Alfresco CM.
It would be nice to have the Web Quick Start predisposed for retrieving content based of some user credentials, as real life web applications often require profiling and content filtering (content available only to registered users, paid content etc). In the meantime I think we will start and do it ourselves. Any suggestion is welcome.
Thank you