Bug 1003003

Summary: Auth config of Modeshape in ER1
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Filip Nguyen <fnguyen>
Component: ModeShapeAssignee: Van Halbert <vhalbert>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: atangrin, fnguyen, hchiorea, ldimaggi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-30 13:26:05 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 Filip Nguyen 2013-08-30 12:59:11 UTC 
JDV6 ER1 Modeshape contains auth configuration that points to non-existent files (see security domain config modeshape-security). I locally reconfigured it to use teiid-security*properties and the authentication started to work on the jcr/dv repo.


This is not blocking issue, as it can be reconfigured by the client.
Comment 2 Horia Chiorean 2013-08-30 13:19:42 UTC 
The ModeShape security domain is configured like this:

<security-domain name="modeshape-security">
<authentication>
  <login-module code="UsersRoles" flag="required">
    <module-option name="usersProperties" value="modeshape-users.properties"/>
    <module-option name="rolesProperties" value="modeshape-roles.properties"/>
  </login-module>
</authentication>
</security-domain>

and the 2 files are located at: jboss-eap-6.1\modules\system\layers\base\org\modeshape\main\conf. 

The "conf" folder exported via:
<resource-root path="conf"/> in ModeShape's main module.xml

Therefore, these files should be accessible (and are present in the kit)
Comment 3 Filip Nguyen 2013-08-30 13:26:05 UTC 
Horia, thanks for the fast and detailed response. You are correct, I must have messed up at some point when running the test.