[
https://issues.apache.org/jira/browse/RANGER-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917490#comment-16917490
]
Peng Xing commented on RANGER-2533:
-----------------------------------
[~madhan.neethiraj], thanks for your suggestion.
{quote}configuration xasecure.audit.is.enabled exists for backward
compatibility with earlier version of Audit configuration (in the code known as
V2 configuration)
{quote}
The user does not know that {{xasecure.audit.is.enabled}} is the V2
configuration, which may cause confusion.
I think this configuration should also apply to the V3 version, and this
configuration will be more convenient to enable/disable audit.
{quote}this change is will disable auditing for all plugins, except the ones
where xasecure.audit.is.enabled is explicitly set to true.
{quote}
After the plugin is installed, {{xasecure.audit.is.enabled}} will be generated
in all {{ranger-xxx-audit.xml}} and the default value is {{true}}.
So in default, this change does not disable audit for all plugins.
{quote}update default value for xasecure.audit.is.enabled as true
{quote}
I agree with you.
.
Thanks
> After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still
> logged
> -----------------------------------------------------------------------------------
>
> Key: RANGER-2533
> URL: https://issues.apache.org/jira/browse/RANGER-2533
> Project: Ranger
> Issue Type: Bug
> Components: audit
> Affects Versions: 2.1.0
> Reporter: Peng Xing
> Assignee: Peng Xing
> Priority: Major
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2533-After-setting-xasecure.audit.is.enabled-.patch
>
>
> After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still
> logged
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
