Admin Console writes incorrect standalone.xml content ----------------------------------------------------- Key: AS7-5500 URL: https://issues.jboss.org/browse/AS7-5500 Project: Application Server 7 Issue Type: Bug Components: Console Environment: Mac OS x 10.6.8, JBoss 7.1.1 Final Reporter: Scott Matthews Labels: admin-console, modules, security-domain I added a Security Domain (manually) to my JBoss application. It included a definition of a custom login module as well as a reference to the module in which it was contained: <login-module code="com.atlassian.crowd.application.jaas.CrowdLoginModule" flag="required" module="com.atlassian.crowd"> Through multiple startups and shutdowns my configuration worked as I expected. When I attempted to use the Admin Console to add new module options to this security domain, my ability to login failed. Upon further investigation I discovered that the admin console removed the module property from the login-module tag. to prove this I repeated the process with the same result.

Admin Console writes incorrect standalone.xml content ----------------------------------------------------- Key: AS7-5500 URL: https://issues.jboss.org/browse/AS7-5500 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Environment: Mac OS x 10.6.8, JBoss 7.1.1 Final Reporter: Scott Matthews Assignee: Tomaz Cerar Labels: admin-console, modules, security-domain Fix For: 7.1.4.Final (EAP) I added a Security Domain (manually) to my JBoss application. It included a definition of a custom login module as well as a reference to the module in which it was contained: <login-module code="com.atlassian.crowd.application.jaas.CrowdLoginModule" flag="required" module="com.atlassian.crowd"> Through multiple startups and shutdowns my configuration worked as I expected. When I attempted to use the Admin Console to add new module options to this security domain, my ability to login failed. Upon further investigation I discovered that the admin console removed the module property from the login-module tag. to prove this I repeated the process with the same result.

Admin Console writes incorrect standalone.xml content ----------------------------------------------------- Key: AS7-5500 URL: https://issues.jboss.org/browse/AS7-5500 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Affects Versions: 7.1.1.Final Environment: Mac OS x 10.6.8, JBoss 7.1.1 Final Reporter: Scott Matthews Assignee: Tomaz Cerar Labels: admin-console, modules, security-domain Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) I added a Security Domain (manually) to my JBoss application. It included a definition of a custom login module as well as a reference to the module in which it was contained: <login-module code="com.atlassian.crowd.application.jaas.CrowdLoginModule" flag="required" module="com.atlassian.crowd"> Through multiple startups and shutdowns my configuration worked as I expected. When I attempted to use the Admin Console to add new module options to this security domain, my ability to login failed. Upon further investigation I discovered that the admin console removed the module property from the login-module tag. to prove this I repeated the process with the same result.

Admin Console writes incorrect standalone.xml content ----------------------------------------------------- Key: AS7-5500 URL: https://issues.jboss.org/browse/AS7-5500 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Affects Versions: 7.1.1.Final Environment: Mac OS x 10.6.8, JBoss 7.1.1 Final Reporter: Scott Matthews Assignee: Tomaz Cerar Labels: admin-console, modules, security-domain Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) I added a Security Domain (manually) to my JBoss application. It included a definition of a custom login module as well as a reference to the module in which it was contained: <login-module code="com.atlassian.crowd.application.jaas.CrowdLoginModule" flag="required" module="com.atlassian.crowd"> Through multiple startups and shutdowns my configuration worked as I expected. When I attempted to use the Admin Console to add new module options to this security domain, my ability to login failed. Upon further investigation I discovered that the admin console removed the module property from the login-module tag. to prove this I repeated the process with the same result.