[jboss-jira] [JBoss JIRA] (AS7-3773) A security realm definition should not require an authentication mechanism to be defined if 'truststore' is defined.

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/AS7-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated AS7-3773:
------------------------------

    Fix Version/s: 7.1.2.Final
                       (was: 7.1.1.Final)


This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers, and EAP LA issues (which are probably not yet at the right status, or need an extra triage pass).

If these issues are completed in a 7.1.1 timeframe please change the fix version. Although if you forget I will bulk correct.
                
> A security realm definition should not require an authentication mechanism to be defined if 'truststore' is defined.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-3773
>                 URL: https://issues.jboss.org/browse/AS7-3773
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management, Security
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 7.1.2.Final
>
>
> On slave DC security realm defined with only a trust store initialising the native interface raised the following error: -
> [Host Controller] 16:24:15,297 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017113: Failed to start service
> [Host Controller] 	at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:112) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
> [Host Controller] 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> [Host Controller] 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> [Host Controller] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [Host Controller] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [Host Controller] 	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> [Host Controller] Caused by: java.lang.IllegalStateException: JBAS017119: A security realm has been specified but no supported mechanism identified
> [Host Controller] 	at org.jboss.as.remoting.RealmSecurityProvider.getOptionMap(RealmSecurityProvider.java:137) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
> [Host Controller] 	at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
> [Host Controller] 	... 5 more
> On a related note - if the native interface of the HC failed to start we should probably avoid starting the AS processes as we know there is nothing for them to connect back to.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira