Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008S3em Steps to Reproduce: Install the SOA suite and the EDS components as per normal. Use JBoss Developer Studio to create two datasources and configure them in a VDB; deploy the VDB and test with the SQL scrapbook. Once this is working, stop SOA. Then follow the procedure as documented in https://access.redhat.com/kb/docs/DOC-19884 for all datasources used by the VDB. Note that you will need multiple application-policy with a different setting for domain=ServerMasterPassword Use the modified name in the MBean in the datasource file. You can of course use a single server.password file. Start SOA and connect via the SQL scrapbook again. This time a query will fail, and in the server.log you will find ("myuser" being the username of the datasource being exercised with your query) 2011-10-28 16:53:32,021 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=mbpF0FFphSOG.0.1.0 java.lang.SecurityException: Unauthenticated caller:myuser at org.jboss.security.integration.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:92) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:687) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:495) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:245) at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:80) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:198) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) project_key: SOA Encrypt the datasource password with procedure in https://access.redhat.com/kb/docs/DOC-19884 the teiid VDB will throw "Unauthenticated caller" when
Link: Added: This issue Cloned to SOA-3536
Link: Removed: This issue Cloned to SOA-3536
Link: Added: This issue Cloned to TEIID-1799
Link: Added: This issue Cloned to SOA-3537
Link: Removed: This issue Cloned to SOA-3537
Link: Added: This issue Cloned to SOA-3538
Please read the comments in TEIID-1799 as to how they were able to get it to work.
Please re-read my description. I use TWO datasources I did use login-conf.xml and not that teiid xml you mention.
Hi Tom. Hey, wouldn't we use the procedures outlined in Section 8.7 of the 5.1 Services Guide instead of using this KB article? Please have a look, let us know if those instructions would apply (and if they would, if it fixes this problem.) Thanks, Rick
Hi Rick, I tested that procedure: does not work. Seems it might work if the the password was a <property> tag (as documented for the messaging example), but the datasource uses a <password> tag and substitution just fails Kind regards Tom
The suggestion above (to use tips in Section 8.7 of the 5.1 Services Guide) didn't pan out.
Attachment: Added: jdbc.war
Closing as not a bug. The real issue seems to be when using Teiid Designer mixing usernames up. (user error)