[ 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? -- This message was sent by Atlassian JIRA (v6.3.15#6346)