- yes only id and user name (the key used to search the user in the module). - from the portal perspective no fields should be mandatory. But that should be configurable from the metadata mapping. For example, someone is doing a portal that requires the email to be always provided then it should be described in the profile metadata. - "theme" is a fake/wrong (i.e hack) profile information. Normally it should not be stored in the user profile but rather in a personalization repository that the portal would manage. - bottom line, the UserModule should never persist profile information (because it's the role of the ProfileModule). UserModule responsibility is to provide authentication only. - probably that we can have 2 profiles modules, one that maps on the identity store which contains enterprise informations. One that stores info in the database and stores portal related informations (like the favorite theme). We should explore that way in a separate thread. - I don't like the UserProfileModule.isMapped, it is just a short cut for a complete metadata API, one should rather do smth like : | profile.getInfo().getAttributeInfo("blah"); | we can spend some time designing the metadata API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987167#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...