[teiid-issues] [JBoss JIRA] (TEIID-2294) Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins reopened TEIID-2294:
-----------------------------------

      Assignee: Steven Hawkins  (was: Ramesh Reddy)


Setting the alias to use will result in a no cipher suites in common error as we are not extending the X509ExtendedKeyManager which is required when using an SSLEngine.
                
> Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer
> ------------------------------------------------------------------------------------------
>
>                 Key: TEIID-2294
>                 URL: https://issues.jboss.org/browse/TEIID-2294
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.0
>            Reporter: Jack Ma
>            Assignee: Steven Hawkins
>              Labels: CR2
>             Fix For: 8.2
>
>
> From the teiid 8.1 schema (jboss-teiid.xsd) under docs, there is no "alias" attribute defined for jdbc transport layer. Here is the question:  in the case of there are multiple certificates defined at  keysore, what certificate jdbc ssl will use? How to specify correct one to use?
>  
> Here is the sample teiid jdbc configuration used:
>    <transport name="jdbc" socket-binding="teiid-jdbc">
>       <authentication security-domain="mysecuritydomain"/>
>       <ssl mode="enabled" keymanagement-algorithm="SunX509">
>           <keystore name="/opt/test.keystore" password="password"/>
>       </ssl>
>    </transport>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira