[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) jira-events at lists.jboss.org
Thu Jul 25 07:02:26 EDT 2013


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

Steven Hawkins resolved TEIID-2294.
-----------------------------------

        Labels:   (was: CR2)
    Resolution: Done


Updated the alias logic to also allow for specifying a key password, used X509ExtendedKeyManager to support key selection for SSLEngines, and updated the docs.
                
> 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
>             Fix For: 8.4.1, 8.5
>
>
> 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


More information about the teiid-issues mailing list