[ http://jira.jboss.com/jira/browse/JBPORTAL-1266?page=comments#action_1235... ] Sohil Shah commented on JBPORTAL-1266: -------------------------------------- This affects only LDAP Identity Module The database based Identity Module is fine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1266?page=comments#action_1235... ] Sohil Shah commented on JBPORTAL-1266: -------------------------------------- This is actually a data booting issue than a bug. The root of the problem is that OpenDS boots in-memory with the portal. Initially, it has no identity data populated, hence the CMS boot policy loads itself, but in the absence of role information in the OpenDS LDAP repo, does not associate the specified permissions with the "User" role. This is not an issue, if the LDAP repository is pre-populated with identity data. However, OpenDS suffers from chicken and egg problem, since you have to run portal to connect to it and import the identity ldif data. Suggested Workaround: 1) Run AS and portal just to load OpenDS data. Once portal is loaded, disregard all error messages. Import the identity ldif data into OpenDS. 2) Once OpenDS is populated in step 1, Stop portal, blow away any portal database data (in case of hypersonic, blow away the data dir), Start portal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira