Hi Ioan, On 20 October 2011 20:52, Ioa Kiss <[email protected]> wrote:
> Hi All, > > I am running some tests with Rave and I find it very interesting. > Good to read :) > > I was wondering about how Rave handles users/account. My understanding is > that Rave is a standalone portal, you create an account and then login and > manage your widgets. Is my assumption correct? > For the demo setup this is true, but the login mechanism is configurable in Spring security. > > I would propose a use case where Rave is a portal that sits on top of > another application and therefore the accounts are uploaded and not created > by a user. Such uploading could happen in different ways. > > 1. One way would be an LDAP connector with LDAP bind authentication > and the ability to upload profile data from LDAP. > Spring security supports LDAP, so that should be possible: http://static.springsource.org/spring-security/site/docs/3.0.x/reference/ldap.html > > 2. Another way would be openID where you authenticate against an > existing application that is an openID provider. You then want to build an > ability to add a plugin that connects into a proprietary REST API to upload > profile data (i.e. when a user logs in for the first time using openID, the > account in Rave is automatically created and the profile data uploaded). > Once the account exists you have to be able to sync profile changes both > ways. > In the demo setup there's already OpenId configuration present. OpenId comes out of the box with Spring security. It is pretty easy to create a new user from an external source such as LDAP or Shibboleth. I used http://wiki.aaf.edu.au/aaf-mini-grants/tpac/shibboleth-integration-with-spring-securityas a starting point of how to login with an external source and creating a new User in the database. Another question is related to the database used by Rave. I noticed that > currently MySQL is used as database. I was wondering what do you think > about > using a NoSQL DB with Rave? I think this would give Rave better scale and > the possibility for redundancy. > The default database is H2, but it is possible to replace that with MySQL (that's what's documented on the site). There's no specific reason why there's no NoSQL support yet. Jasha Joachimsthal Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free) www.onehippo.com
