...
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Vinny Khosla asked on the JASIG-PORTAL list: How do i setup a user layout template? Could you please tell me what tables, columns and xml files are involved Do the new users automatically inherit the layout template? |
...
The IUserIdentityStore interface is the mechanism for retrieving the unique identifier for the current user in the portal. There is one implementation of this interfact: RDBMUserIdentityStore. Two properties as well as the value of person attributes for the user affect how this class makes the choice of template.
- The property
autoCreateUsersturns template behavior on or off. As distributed the property is set:
When set to true,Code Block org.jasig.portal.services.Authentication.autoCreateUsers=trueRDBMUserIdentityStorewill automatically create all necessary data for a new portal user based on a template user. If set to false users data will not be automatically created. So far there is no other mechanism for creating user data so this property is always set to true.
- The template user value is determined either by the property
defaultTemplateUserNameor by mapping a directory attribute to uPortalTemplateUserName. When a user logs in for the first time,RDBMUserIdentityStorefirst looks for a person attribute nameduPortalTemplateUserName. The value of that attribute is expected to be the username of an existing user. The existing user is then the template for the new user. If no attribute is of that name is mapped the template user name comes from the propertyorg.jasig.portal.services.Authentication.defaultTemplateUserName. In the distribution this is set to the userdemo:
This means that if you make no changes and map no attribute to uPortalTemplateUserName then all new users will be cloned from the userCode Block org.jasig.portal.services.Authentication.defaultTemplateUserName=demodemo.
Templates and layout managers
...