[JBoss JIRA] Created: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
3:40 p.m.
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
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
3:42 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Justin Bertram updated JBTM-666:
--------------------------------
Assignee: Jonathan Halliday
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
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
3:44 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
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_...
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
3:50 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Justin Bertram updated JBTM-666:
--------------------------------
Component/s: Recovery
Affects Version/s: 4.2.3.CP05
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)
Components: Recovery
Affects Versions: 4.2.3.CP05
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
8:33 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Justin Bertram updated JBTM-666:
--------------------------------
Comment: was deleted
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)
Components: Recovery
Affects Versions: 4.2.3.CP05
Reporter: Justin Bertram
Assignee: Jonathan Halliday
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
8:33 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Justin Bertram updated JBTM-666:
--------------------------------
Attachment: (was: AppServerJDBCXARecovery.java)
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)
Components: Recovery
Affects Versions: 4.2.3.CP05
Reporter: Justin Bertram
Assignee: Jonathan Halliday
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
8:39 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
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_...
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)
Components: Recovery
Affects Versions: 4.2.3.CP05
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
8:48 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Jonathan Halliday updated JBTM-666:
-----------------------------------
Fix Version/s: 4.2.3.SP8
4.2.3.CP09
4.10.0
4.6.1.CP04
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)
Components: Recovery
Affects Versions: 4.2.3.CP05
Reporter: Justin Bertram
Assignee: Jonathan Halliday
Fix For: 4.2.3.SP8, 4.2.3.CP09, 4.10.0, 4.6.1.CP04
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
7:37 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Jonathan Halliday updated JBTM-666:
-----------------------------------
Affects Version/s: 4.6.1.CP03
4.9.0
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)
Components: Recovery
Affects Versions: 4.2.3.CP05, 4.9.0, 4.6.1.CP03
Reporter: Justin Bertram
Assignee: Jonathan Halliday
Fix For: 4.2.3.SP8, 4.2.3.CP09, 4.10.0, 4.6.1.CP04
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
7:37 a.m.
New subject: [JBoss JIRA] Closed: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule
[
https://jira.jboss.org/jira/browse/JBTM-666?page=com.atlassian.jira.plugi...
]
Jonathan Halliday closed JBTM-666.
----------------------------------
Resolution: Done
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)
Components: Recovery
Affects Versions: 4.2.3.CP05, 4.9.0, 4.6.1.CP03
Reporter: Justin Bertram
Assignee: Jonathan Halliday
Fix For: 4.2.3.SP8, 4.2.3.CP09, 4.10.0, 4.6.1.CP04
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
4899
days inactive
4928
days old
jbossts-issues@lists.jboss.org
9 comments
2 participants
participants (2)
-
Jonathan Halliday (JIRA) -
Justin Bertram (JIRA)