Github user sudheeshkatkam commented on a diff in the pull request:
https://github.com/apache/drill/pull/773#discussion_r114215418
--- 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_ENCRYPTION_SASL_ENABLED =
"drill.exec.security.user.encryption.sasl.enabled";
+ String USER_ENCRYPTION_SASL_MAX_WRAPPED_SIZE =
"drill.exec.security.user.encryption.sasl.max_wrapped_size";
--- End diff --
We should document this config parameter due to the change in name (from
"maximum size of the raw send buffer in bytes" to max_wrapped_size).
From [Sasl.RAW_SEND_SIZE
doc](http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/javax/security/sasl/Sasl.java#151):
> The name of a property that specifies the maximum size of the raw send
buffer in bytes of SaslClient/SaslServer. The property contains the string
representation of an integer. The value of this property is negotiated between
the client and server during the authentication exchange.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
