[jboss-jira] [JBoss JIRA] (SECURITY-750) Database*LoginModules should use the transactionManagerJndiName module option

[Stefan Guilhen (JIRA)]

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

Stefan Guilhen closed SECURITY-750.
-----------------------------------

    Resolution: Done


DButils.getRolesSet() method now receives the TxManagerJNDIName as a parameter. Both DBLoginModules now allow configuration of the txManagerJNDI name and they both propagate the configured value (or the default java:/TransactionManager) to DBUtils when getting the roles.
                
> Database*LoginModules should use the transactionManagerJndiName module option
> -----------------------------------------------------------------------------
>
>                 Key: SECURITY-750
>                 URL: https://issues.jboss.org/browse/SECURITY-750
>             Project: PicketBox 
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: PicketBox
>            Reporter: Stefan Guilhen
>            Assignee: Stefan Guilhen
>             Fix For: PIcketBox_4_0_19.Final
>
>
> The DatabaseCertLoginModule and DatabaseServerLoginModule use for role search a routine from a class org.jboss.security.auth.spi.DbUtil. But there is a hardcoded reference to JNDI name for Transaction Manager lookup "java:/TransactionManager" - which is not valid in the EAP 6. The JNDI name should be provided as a parameter.
> The login module option "transactionManagerJndiName" is already implemented in the DatabaseServerLoginModule, but it should be also added to the DatabaseCertLoginModule.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira