[
https://issues.redhat.com/browse/WFLY-13589?page=com.atlassian.jira.plugi...
]
Paul Ferraro updated WFLY-13589:
--------------------------------
Description:
Infinispan 11.0 requires authentication by default. Consequently, we need the ability to
configure authentication for a remote-cache-container.
See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/]
See
also: [https://infinispan.org/docs/dev/titles/server/server.html#security]
To future-proof this, we should also allow informal adhoc properties (like we already do
for JGroups protocols and cache stores) - which are processed by the hotrod client before
any formal properties from the model.
was:
Infinispan 11.0 requires authentication by default. Consequently, we need the ability to
configure authentication for a remote-cache-container.
See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/]
See
also: [https://infinispan.org/docs/dev/titles/server/server.html#security]
WildFly cannot connect to an infinispan-server cluster requiring
authentication
-------------------------------------------------------------------------------
Key: WFLY-13589
URL:
https://issues.redhat.com/browse/WFLY-13589
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Radoslav Husar
Priority: Critical
Infinispan 11.0 requires authentication by default. Consequently, we need the ability to
configure authentication for a remote-cache-container.
See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/]
See
also: [https://infinispan.org/docs/dev/titles/server/server.html#security]
To future-proof this, we should also allow informal adhoc properties (like we already do
for JGroups protocols and cache stores) - which are processed by the hotrod client before
any formal properties from the model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)