[jbossts-issues] [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
Justin Bertram (JIRA)
jira-events at lists.jboss.org
Mon Dec 7 16:44:29 EST 2009
[ https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated JBTM-666:
--------------------------------
Attachment: AppServerJDBCXARecovery.java
This fix is based off https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_2_3_SP5_CP05_JBTM_432_JBTM_571 as I was testing with JBoss EAP 4.3 CP06 and needed the other fixes.
> Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-666
> URL: https://jira.jboss.org/jira/browse/JBTM-666
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Justin Bertram
> Assignee: Jonathan Halliday
> Attachments: AppServerJDBCXARecovery.java
>
>
> Attempting to recovery failed XA transactions from a datasource using:
> <security-domain>DefaultDSRealm</security-domain>
> Where the security realm's login module implementation is org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule. For example:
> <application-policy name = "DefaultDSRealm">
> <authentication>
> <login-module code = "org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule"
> flag = "required">
> <module-option name = "username">user</module-option>
> <module-option name = "password">oLxZUT0uKnAfS.zbvaEZd</module-option>
> <module-option name = "managedConnectionFactoryName">jboss.jca:service=XATxCM,name=XAOracleDS</module-option>
> <module-option name = "jaasSecurityDomain">jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword</module-option>
> </login-module>
> </authentication>
> </application-policy>
> (See more discussion of this configuration at http://www.jboss.org/community/wiki/encryptingdatasourcepasswords)
> This exception is thrown:
> 2009-12-03 09:53:20,388 ERROR [com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery] (Thread-6:) AppServerJDBCXARecovery.createConnection got exception java.sql.SQLException: Invalid argument(s) in call
> java.sql.SQLException: Invalid argument(s) in call
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:99)
> at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.createConnection(AppServerJDBCXARecovery.java:258)
> at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.getXAResource(AppServerJDBCXARecovery.java:115)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:683)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:179)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163)
> This exception is thrown because com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery is attempting to create a connection without a username and password since it can't decrypt the password from the security domain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list