[JBoss JIRA] (TEIID-2294) Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer
6 p.m.
Jack Ma created TEIID-2294:
------------------------------
Summary: 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
Reporter: Jack Ma
Assignee: Steven Hawkins
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
6:02 p.m.
[
https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin...
]
SBS JIRA Integration updated TEIID-2294:
----------------------------------------
Forum Reference: https://community.jboss.org/message/773335#773335
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
Reporter: Jack Ma
Assignee: Steven Hawkins
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
2:10 p.m.
[
https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-2294:
--------------------------------
Fix Version/s: 8.2
Assignee: Ramesh Reddy (was: Steven Hawkins)
Git Pull Request: https://github.com/teiid/teiid/pull/20
Affects Version/s: 8.0
Complexity: Medium
Component/s: Server
Affects: Documentation (Ref Guide, User Guide, etc.)
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: Ramesh Reddy
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
2:12 p.m.
[
https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-2294.
---------------------------------
Labels: CR2 (was: )
Resolution: Done
Added code to allow the alias name to the ssl key store configuration, so that if the
keystore contains multiple certificates it can choose key by its alias name.
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: Ramesh Reddy
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
4429
days inactive
4434
days old
3 comments
3 participants
participants (3)
-
Jack Ma (JIRA) -
Ramesh Reddy (JIRA)
-
SBS JIRA Integration (JIRA)