[
https://issues.apache.org/jira/browse/ACCUMULO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771995#comment-13771995
]
Christopher Tubbs commented on ACCUMULO-1009:
---------------------------------------------
[~vines]: We can make MAC easy to configure SSL for testing, regardless of
whether the provisioning code is there or not. But what specific security
configuration are you testing by providing a security switch that automatically
provisions and configures MAC?
The described situation is no different than configuring the jetty-maven-plugin
with certs to test a webapp in Jetty with ssl... but you don't see Jetty with a
"do security" configuration option that automatically chooses a security
configuration to test against... you still have to provision certs (generating
certs, using something like keytool-maven-plugin, if testing in maven, or by
providing a specific cert), in order to test the app with that *specific*
security configuration. Testing "security on" is next to meaningless. Testing a
*specific* security configuration is far more valuable to users.
So, I'm not convinced that users will get value from MAC having provisioning
code. However, I *do* think there's value in documenting the provisioning and
configuration of certs (with openssl or keytool) in an example. And... what
would be *really* valuable is having this done automatically in an integration
test baked-in to the next version of the Instamo maven archetype that supports
SSL.
> Support encryption over the wire
> --------------------------------
>
> Key: ACCUMULO-1009
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1009
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Keith Turner
> Assignee: Michael Berman
> Fix For: 1.6.0
>
> Attachments: ACCUMULO-1009_thriftSsl.patch
>
>
> Need to support encryption between ACCUMULO clients and servers. Also need
> to encrypt communications between server and servers.
> Basically need to make it possible for users to enable SSL+thrift.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
