Bug 779181 (SOA-1576) - JBossWS policy of login-config.xml is set to non-existing jmx-console-*.properties files
Summary: JBossWS policy of login-config.xml is set to non-existing jmx-console-*.prope...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1576
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Configuration
Version: 5.0.0 ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.0 GA,5.0.0 ER2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-02 09:40 UTC by Pavel Macik
Modified: 2010-01-04 15:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 15:59:07 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1576 0 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.