[
https://issues.apache.org/jira/browse/DRILL-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957884#comment-15957884
]
ASF GitHub Bot commented on DRILL-4335:
---------------------------------------
Github user sudheeshkatkam commented on a diff in the pull request:
https://github.com/apache/drill/pull/773#discussion_r109729986
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/ExecConstants.java ---
@@ -116,6 +116,11 @@
String BIT_AUTHENTICATION_ENABLED =
"drill.exec.security.bit.auth.enabled";
String BIT_AUTHENTICATION_MECHANISM =
"drill.exec.security.bit.auth.mechanism";
String USE_LOGIN_PRINCIPAL =
"drill.exec.security.bit.auth.use_login_principal";
+ String USER_SASL_ENCRYPTION_ENABLED =
"drill.exec.security.user.sasl.encryption.enabled";
--- End diff --
How about using "drill.exec.security.user.**encryption.sasl**.enabled"
instead of "drill.exec.security.user.**sasl.encryption**.enabled" to be
consistent with "auth" (and similarly below)?
> Apache Drill should support network encryption
> ----------------------------------------------
>
> Key: DRILL-4335
> URL: https://issues.apache.org/jira/browse/DRILL-4335
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Keys Botzum
> Assignee: Sorabh Hamirwasia
> Labels: security
> Attachments: ApacheDrillEncryptionUsingSASLDesign.pdf
>
>
> This is clearly related to Drill-291 but wanted to make explicit that this
> needs to include network level encryption and not just authentication. This
> is particularly important for the client connection to Drill which will often
> be sending passwords in the clear until there is encryption.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
