Bug 779181 (SOA-1576)

Summary: JBossWS policy of login-config.xml is set to non-existing jmx-console-*.properties files
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Pavel Macik <pmacik>
Component: ConfigurationAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER1CC: darran.lofthouse
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1576
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-04 15:59:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavel Macik 2009-11-02 09:40:55 UTC
Date of First Response: 2009-11-04 06:52:13
Workaround: Workaround Exists
Workaround Description: Either the missing files should be added or the configuration should be changed to "jbossws-{users,roles}.properties"
project_key: SOA

$[SOA_HOME]/jboss-as/server/{all,default,production}/conf/login-config.xml files contains following code snippet that refers to non-existing jmx-console-*.properties files.

login-config.xml:
...
 <application-policy name="JBossWS"> 
      <authentication> 
         <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> 
            <module-option name="usersProperties">props/jmx-console-users.properties 
            </module-option> 
            <module-option name="rolesProperties">props/jmx-console-roles.properties 
            </module-option> 
         </login-module> 
      </authentication> 
   </application-policy><!--- - - - --><!--Loaded from orignal file: old/login-config.xml-->
...

Either the missing files should be added or the configuration should be changed to "jbossws-{users,roles}.properties"

Comment 1 Pavel Macik 2009-11-02 10:16:52 UTC
Workaround Description: Removed: Either the missing files should be added or the configuration should be changed to "soa-{users,roles}.properties" Added: Either the missing files should be added or the configuration should be changed to "jbossws-{users,roles}.properties"


Comment 2 Darran Lofthouse 2009-11-04 11:52:13 UTC
This issue may be slightly out of date, for EAP 5 the application-policy has been reverted to: -

  <application-policy name="JBossWS">
    <authentication>
      <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
        flag="required">
        <module-option name="usersProperties">props/jbossws-users.properties</module-option>
        <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
        <module-option name="unauthenticatedIdentity">anonymous</module-option>
      </login-module>
    </authentication>
  </application-policy>

However the default user in jbossws-users.properties is commented out.

Comment 3 trev 2009-11-05 09:58:03 UTC
Link: Added: This issue is related to JBPAPP-2790


Comment 4 trev 2009-11-05 10:01:05 UTC
The EAP application-policy was reverted because the  WS unit tests need this entry. 
Will match the EAP changes.

Comment 5 Jiri Pechanec 2010-01-04 15:59:07 UTC
Verified in ER6 - policy is set and directed to present configuration files with disabled default user and role