[DOCU-845] Update page JBoss AS configuration Created: 13/Oct/16  Updated: 03/Jul/17  Resolved: 25/Oct/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: core
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File magnolia549onWildfly10.png     PNG File magnolia55snaponWildfly10.png    
Issue Links:
documentation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:

 Description   

Update https://documentation.magnolia-cms.com/display/DOCS/JBoss+AS+configuration.

Changes on configuration can be seen on DEV-303
Attention:

  • Some of the changes are for 5.5 only
  • Some changes concern both 5.5 and 5.4


 Comments   
Comment by Martin Drápela [ 20/Oct/16 ]

Checked the DEV-303 configs and it is in fact possible to get both Magnolias (5.4.9 + 5.5) running on Wildfly 10.1.0.Final by just adding the following XML to $Wildfly_dir/standalone/configuration/standalone.xml:

<security-domain name="magnolia" cache-type="default">
  <authentication>
     <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthenticationModule" flag="requisite"/>
     <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthorizationModule" flag="required"/>
   </authentication>
</security-domain>

As for the the configs for the <module xmlns="urn:jboss:module:1.1" name="org.bouncycastle"> node in $Wildfly_dir/modules/system/layers/base/org/bouncycastle/main/module.xml, Wildfly 10.1.0.Final has

<module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
    <properties>
        <property name="jboss.api" value="private"/>
    </properties>
    <resources>
        <resource-root path="bcprov-jdk15on-1.52.jar"/>
        <resource-root path="bcmail-jdk15on-1.52.jar"/>
        <resource-root path="bcpkix-jdk15on-1.52.jar"/>
    </resources>
    <dependencies>
        <module name="javax.api"/>
        <module name="javax.mail.api" optional="true"/>
        <module name="javax.activation.api" optional="true"/>
    </dependencies>
</module>

but upon deployment of Magnolia to WIldfly, the Magnolia-internal Bouncy configs are probably applied from /WEB-INF/jboss-deployment-structure.xml where Magnolia 5.5 has

<resources>
      <resource-root path="WEB-INF/lib/bcprov-jdk15on-1.54.jar" use-physical-code-source="true"/>
      <resource-root path="WEB-INF/lib/bcpg-jdk15on-1.54.jar" use-physical-code-source="true"/>
      <resource-root path="WEB-INF/lib/bcmail-jdk15on-1.54.jar" use-physical-code-source="true"/>
</resources>

while Magnolia 5.4.9 has

    <resources>
      <resource-root path="WEB-INF/lib/bcprov-jdk15on-1.46.jar" use-physical-code-source="true"/>
      <resource-root path="WEB-INF/lib/bcpg-jdk15on-1.46.jar" use-physical-code-source="true"/>
      <resource-root path="WEB-INF/lib/bcmail-jdk15on-1.46.jar" use-physical-code-source="true"/>
    </resources>
Comment by Martin Drápela [ 25/Oct/16 ]

The JBoss AS config page in 5.4 DOCspace (https://documentation.magnolia-cms.com/display/DOCS54/Wildfly+%28JBoss+AS%29+configuration) has been modified according to the information in DEV-303 and the config page was renamed to Wildfly (JBoss AS) configuration.

In 5.5 DOCspace the JAAS configuration has been moved from the config subpage (link in the next sentence) to the main page (https://documentation.magnolia-cms.com/display/DOCS/Deploying+a+WAR+on+Wildfly+%28JBoss%29+application+server) so that users can successfully login to Magnolia after deployment.

The configuration subpage (https://documentation.magnolia-cms.com/display/DOCS55/%28UPDATE-NEEDED%29+Other+Wildfly+configuration+options) however needs a thorough review - some things on it are probably obsolete (references to JBoss 6/7 etc.).

Generated at Mon Feb 12 01:12:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.