[JBoss JIRA] (TEIID-3493) Use certificates in Salesforce SOAP API calls
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3493?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3493:
-------------------------------------
I spent couple hours looking into what we can do for this, here is my analysis. As Steve mentions there is no Parter API supported code or even generated code will automatically will give us ability to configure a client certificate in pkcs12 format and ans send it along with every web service call. However, in Partner API, in the "ConnectorConfig" class, gives a way to configure an external Transport class, the default configured class is JdkHttpTransport.class which only understands "HTTP". I believe, this issue needs to use "HTTPS" and negotiate mutual auth in TLS connection that is made from client side, and that is only difference from normal connection (excluding the setup on the SF side).
Now, we have two possible extensions, I can think of
1. Extend the JdkHttpTransport class, to support HTTPS based on configuration defined in ra.xml for client certificates, passcodes etc.
2. Some how integrate CXF based transport here, then configuration can be delegated to the spring configuration file. The advantage with this is, we do not have to define any new configuration, and supporting other authentication protocols such as OAuth should be possible.
What do you think?
> Use certificates in Salesforce SOAP API calls
> ---------------------------------------------
>
> Key: TEIID-3493
> URL: https://issues.jboss.org/browse/TEIID-3493
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Burak Serdar
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Currently salesforce connector supports user/password authentication. It would be nice if we can use certificates.
> https://help.salesforce.com/apex/HTViewHelpDoc?id=security_keys_uploading...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3578:
-------------------------------------
Assignee: Van Halbert (was: Steven Hawkins)
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Van Halbert
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3594:
---------------------------------------
Since JBoss logging doesn't expose a FINER level, there isn't a great way to do this through just standard logging unless we demote the source events to trace level. Moving the user query events up to info would be too verbose by default.
> Change the default for command logging to write User query (start/end)
> ----------------------------------------------------------------------
>
> Key: TEIID-3594
> URL: https://issues.jboss.org/browse/TEIID-3594
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example:
> - default, log the user query start and end entry
> - debug, log the use query and the source queries
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3539) Infinispan-dsl-cache translator: Can't use IS [NOT] NULL operator for non-string columns
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3539?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3539:
----------------------------------
Fix Version/s: 8.7.1.6_2
8.12
> Infinispan-dsl-cache translator: Can't use IS [NOT] NULL operator for non-string columns
> ----------------------------------------------------------------------------------------
>
> Key: TEIID-3539
> URL: https://issues.jboss.org/browse/TEIID-3539
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1.6_2
> Reporter: Filip Elias
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2, 8.12
>
> Attachments: server.log
>
>
> If I use IS NULL or IS NOT NULL operator for non-string column, the server will throw the following exception:
> {code}
> 10:42:34,100 ERROR [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue151) Connector worker process failed for atomic-request=1LH0VEAxBj0U.40.0.30: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[176] returned server error (status=0x85): org.hibernate.search.SearchException: Cannot create numeric range query for field byteNum, since from and to values are null
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:57)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:24)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:50)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:72)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:62)
> at org.teiid.translator.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:112)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3539) Infinispan-dsl-cache translator: Can't use IS [NOT] NULL operator for non-string columns
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3539?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3539.
--------------------------------
Resolution: Done
Resolving this as this issue was changed based on TEIID-3573 and the supportNot and supportNull have been disabled.
> Infinispan-dsl-cache translator: Can't use IS [NOT] NULL operator for non-string columns
> ----------------------------------------------------------------------------------------
>
> Key: TEIID-3539
> URL: https://issues.jboss.org/browse/TEIID-3539
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1.6_2
> Reporter: Filip Elias
> Assignee: Van Halbert
> Attachments: server.log
>
>
> If I use IS NULL or IS NOT NULL operator for non-string column, the server will throw the following exception:
> {code}
> 10:42:34,100 ERROR [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue151) Connector worker process failed for atomic-request=1LH0VEAxBj0U.40.0.30: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[176] returned server error (status=0x85): org.hibernate.search.SearchException: Cannot create numeric range query for field byteNum, since from and to values are null
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:57)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:24)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:50)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:72)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:62)
> at org.teiid.translator.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:112)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months