[
https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin....
]
Wolf-Dieter Fink commented on ISPN-7392:
----------------------------------------
This server configuration is expected to work:
<subsystem xmlns="urn:infinispan:server:endpoint:8.0">
<hotrod-connector cache-container="local"
socket-binding="hotrod">
<topology-state-transfer lazy-retrieval="false"
lock-timeout="1000" replication-timeout="5000"/>
<authentication security-realm="ApplicationRealm">
<sasl mechanisms="PLAIN"
server-name="myServer">
<policy>
<no-anonymous value="true"/>
</policy>
</sasl>
</authentication>
</hotrod-connector>
As workaround SASL properties can be used:
<subsystem xmlns="urn:infinispan:server:endpoint:8.0">
<hotrod-connector cache-container="local"
socket-binding="hotrod">
<topology-state-transfer lazy-retrieval="false"
lock-timeout="1000" replication-timeout="5000"/>
<authentication security-realm="ApplicationRealm">
<sasl mechanisms="PLAIN"
server-name="myServer">
<property
name="javax.security.sasl.policy.noanonymous">true</property>
</sasl>
</authentication>
</hotrod-connector>
The policy elements are ignored in the server sasl configuration
----------------------------------------------------------------
Key: ISPN-7392
URL:
https://issues.jboss.org/browse/ISPN-7392
Project: Infinispan
Issue Type: Bug
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Server SASL mech policies can be specified via properties or policy elements. When using
the latter, the policy elements are not converted to the corresponding properties and
applied to the mech config
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)