[infinispan-dev] Hot Rod secured by default

Sebastian Laskawiec slaskawi at redhat.com
Thu Mar 30 08:54:06 EDT 2017

I agree the security out of the box is good. But at the same time we don't
want to make Infinispan harder to use for new developers. Out of the box
configuration should be "good enough" to start hacking.

I would propose to make all the endpoints unprotected (with authentication
disabled) on localhost/loopback and protected when calling from the outside

On Thu, Mar 30, 2017 at 2:39 PM Tristan Tarrant <ttarrant at redhat.com> wrote:

> Dear all,
> after a mini chat on IRC, I wanted to bring this to everybody's attention.
> We should make the Hot Rod endpoint require authentication in the
> out-of-the-box configuration.
> The proposal is to enable the PLAIN (or, preferably, DIGEST) SASL
> mechanism against the ApplicationRealm and require users to run the
> add-user script.
> This would achieve two goals:
> - secure out-of-the-box configuration, which is always a good idea
> - access to the "protected" schema and script caches which is prevented
> when not on loopback on non-authenticated endpoints.
> Tristan
> --
> Tristan Tarrant
> Infinispan Lead
> JBoss, a division of Red Hat
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20170330/8f1e51ae/attachment.html 

More information about the infinispan-dev mailing list