Bug 793639 (JBEPP-718)

I sent you by email the case and attachments.

Release Notes Docs Status: Added: Not Yet Documented

Primary SME: Added: theute

Labels: Added: EPP_5_2_1_Candidate

Labels: Removed: EPP_5_2_1_Candidate 

Other related HelpDesk Ticket: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007su0S&sfdc.override=1

This is implemented in https://github.com/gatein/gatein-toolbox/tree/master/CoreOrganizationInitializer. 

We agreed with Thomas and Honza to fork those classes into EPP (and not GateIn) so it is packaged together. I think it can go into component.identity. 

Configuration xml should be copied over and exposed in some easy to access place (idm-configuration.xml or some separate initializer-configuration.xml with import that is commented out by default).

I added new component exo.portal.component.initializer for this stuff and I copy all the sources from https://github.com/gatein/gatein-toolbox/tree/master/CoreOrganizationInitializer into this component. I added new configuration file web/portal/src/main/webapp/WEB-INF/conf/organization/initializer-configuration.xml, which is linked from web/portal/src/main/webapp/WEB-INF/conf/configuration.xml but it's commented by default. So initializer is commented by default and can be uncommented on demand when needed.

New Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=801424 has been created for Jared to add section about initializer into Reference guide.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
CAUSE: When portal administrator adds user or group through EPP UI (Organization API) then all necessary objects are created for this user or group in JCR. But when he adds them directly into his database or ldap, then JCR objects are not created because some necessary listeners are not triggered.

CONSEQUENCE: It may lead to bugs and exceptions in some situations, because needed JCR objects for particular user or group are not correctly initialized.

FIX:
CoreOrganizationInitializer is plugin has been createdL.

Purpose of CoreOrganizationInitializer is to trigger all necessary listeners for objects, which were created externally. It's useful especially when you are using
EPP-SP but may be useful also for plain EPP.

RESULT: CoreOrganizationInitializer plugin bundled in EPP. This plugin is disabled by default but can be enabled by portal administrator in configuration when needed. Section into Reference guide has been added to document this new feature.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -3,9 +3,9 @@
 CONSEQUENCE: It may lead to bugs and exceptions in some situations, because needed JCR objects for particular user or group are not correctly initialized.
 
 FIX:
-CoreOrganizationInitializer is plugin has been createdL.
+CoreOrganizationInitializer plugin has been created.
 
 Purpose of CoreOrganizationInitializer is to trigger all necessary listeners for objects, which were created externally. It's useful especially when you are using
 EPP-SP but may be useful also for plain EPP.
 
-RESULT: CoreOrganizationInitializer plugin bundled in EPP. This plugin is disabled by default but can be enabled by portal administrator in configuration when needed. Section into Reference guide has been added to document this new feature.+RESULT: CoreOrganizationInitializer plugin bundled in EPP. This plugin is disabled by default but can be enabled by portal administrator in configuration when needed. Section into Reference guide will be added to document this new feature.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,11 +1 @@
-CAUSE: When portal administrator adds user or group through EPP UI (Organization API) then all necessary objects are created for this user or group in JCR. But when he adds them directly into his database or ldap, then JCR objects are not created because some necessary listeners are not triggered.
+If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in WEB-INF/conf/organization/initializer-configuration.xml.-
-CONSEQUENCE: It may lead to bugs and exceptions in some situations, because needed JCR objects for particular user or group are not correctly initialized.
-
-FIX:
-CoreOrganizationInitializer plugin has been created.
-
-Purpose of CoreOrganizationInitializer is to trigger all necessary listeners for objects, which were created externally. It's useful especially when you are using
-EPP-SP but may be useful also for plain EPP.
-
-RESULT: CoreOrganizationInitializer plugin bundled in EPP. This plugin is disabled by default but can be enabled by portal administrator in configuration when needed. Section into Reference guide will be added to document this new feature.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in WEB-INF/conf/organization/initializer-configuration.xml.+If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in EPP_HOME/server/<PROFILE>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml to import file initializer-configuration.xml .

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in EPP_HOME/server/<PROFILE>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml to import file initializer-configuration.xml .+If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the static configuration stored in the initializer-configuration.xml file .

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the static configuration stored in the initializer-configuration.xml file .+If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the  configuration stored in the initializer-configuration.xml file.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the  configuration stored in the initializer-configuration.xml file.+If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, which imports the  configuration stored in the initializer-configuration.xml file.

Verified the issue when initializer is used/not used for scenario with ACME ldap user. (epp + sp + acme)

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.