Yes securing the cluster channel is available only in enterprise Hazelcast & for 4.4 based releases, it requires a kernel patch we have released as well. On Jun 14, 2016 12:22 PM, "Srinath Perera" <[email protected]> wrote:
> I think it is only for enterprise version. > > Right deployment architecture is to secure it through a firewall. > Basically, only designated nodes should be able to connect to the hazelcast > cluster. > > --srinath > > > > On Mon, Jun 13, 2016 at 10:36 PM, Hasitha Hiranya <[email protected]> > wrote: > >> Hi, >> >> When a cluster is setup out of WSO2 servers Hazelcast is configured to >> >> 1. Make cluster calls across nodes (push notifications) >> 2. Use as a distributed cache among the nodes >> >> Is there any possibility for a third party Hazelcast client to come and >> consume this data or push un-relevant notifications to the nodes? Also, are >> we storing sensitive data in HZ cache? >> >> Hazelcast communication is happening inside MZ. But yet some companies >> would like to make it secured. >> >> SSL can be configured at HZ client level as per [1], but not sure if it >> only for enterprise. >> >> [1]. http://docs.hazelcast.org/docs/3.5/manual/html/ssl.html >> >> Thanks >> >> -- >> *Hasitha Abeykoon* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> > > > -- > ============================ > Blog: http://srinathsview.blogspot.com twitter:@srinath_perera > Site: http://home.apache.org/~hemapani/ > Photos: http://www.flickr.com/photos/hemapani/ > Phone: 0772360902 >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
