[
https://issues.jboss.org/browse/JGRP-1883?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1883:
--------------------------------
No, don't close it yet ! I was just assessing your argument and if marketing/prod mgmt
thinks that we need to support SASL all the way, then fine. Is this the case ?
It's just that I wouldn't be able to do this, so if you or Tristan have time, no
problem...
Your argument that the SASL tools get enhanced outside of JGroups and then we benefit from
that work by upgrading the SASL lib is certainly valid.
I think you and Tristan need to discuss this (and perhaps Divya)...
Extend SASL protocol to handle Quality of Protection
-----------------------------------------------------
Key: JGRP-1883
URL:
https://issues.jboss.org/browse/JGRP-1883
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.5
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Fix For: 3.6
SASL implementations generally provide authentication and encryption services to
communication protocols.
At present, the JGroups SASL protocol layer handles only authentication of a client
joining a group; it does not support encryption of messages (unicast and multicast)
passing through the SASL layer. This is presently handled by the separate ENCRYPT layer.
It would be nice to provide an integrated and complete solution for authentication and
encryption for JGroups based on SASL. This could be achieved by adding functionality from
ENCRYPT to the SASL layer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)