[JBoss JIRA] (ISPN-5721) Add SNI support to the endpoints
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-5721?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-5721:
-------------------------------------------
Progress tracked in Sub tasks
> Add SNI support to the endpoints
> --------------------------------
>
> Key: ISPN-5721
> URL: https://issues.jboss.org/browse/ISPN-5721
> Project: Infinispan
> Issue Type: Feature Request
> Components: Security, Server
> Affects Versions: 8.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Sebastian Łaskawiec
> Fix For: 9.0.0.Alpha2
>
>
> Openshift Router uses DNS names to perform routing. It is perfectly legal to have this kind of configuration:
> {code}
> client 1 --> example.com:11222 -----+> Hotrod server
> /
> client 2 --> example2.com:11222 /
> {code}
> In that case the TLS configuration might be problematic (since very often certificates are issued for a domain name). However it is possible to use [SNI TLS Extension|https://tools.ietf.org/html/rfc6066#page-6].
> The SNI needs to be added to:
> * Client's configuration (it needs to modify it's own {{SSLContext}} and add {{SSLParams}}
> * Hotrod server to support SNI (with Netty)
> * XML Configuration for Hotrod
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5721) Add SNI support to the endpoints
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-5721?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-5721:
--------------------------------------
Status: Pull Request Sent (was: Open)
> Add SNI support to the endpoints
> --------------------------------
>
> Key: ISPN-5721
> URL: https://issues.jboss.org/browse/ISPN-5721
> Project: Infinispan
> Issue Type: Feature Request
> Components: Security, Server
> Affects Versions: 8.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Sebastian Łaskawiec
> Fix For: 9.0.0.Alpha2
>
>
> Openshift Router uses DNS names to perform routing. It is perfectly legal to have this kind of configuration:
> {code}
> client 1 --> example.com:11222 -----+> Hotrod server
> /
> client 2 --> example2.com:11222 /
> {code}
> In that case the TLS configuration might be problematic (since very often certificates are issued for a domain name). However it is possible to use [SNI TLS Extension|https://tools.ietf.org/html/rfc6066#page-6].
> The SNI needs to be added to:
> * Client's configuration (it needs to modify it's own {{SSLContext}} and add {{SSLParams}}
> * Hotrod server to support SNI (with Netty)
> * XML Configuration for Hotrod
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6540) Management console doesn't display cache containers correctly if there are two containers with the same name
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6540?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6540:
------------------------------
Summary: Management console doesn't display cache containers correctly if there are two containers with the same name (was: Management console - doesn't display cache containers correctly if there are two containers with the same name)
> Management console doesn't display cache containers correctly if there are two containers with the same name
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6540
> URL: https://issues.jboss.org/browse/ISPN-6540
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Roman Macor
> Attachments: Screenshot-containersWithSameName.png, Screenshot-detalPageForBothContainers.png
>
>
> When we have two containers with the same name on different clusters some values are displayed correctly - #caches, name, clustering-info, but some are not - endpoints, sites.
> Additionally, clicking on either of containers display the same information, even though containers are configured differently.
> Please see the screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months