[ https://issues.apache.org/jira/browse/RANGER-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhay Kulkarni updated RANGER-1535:
-----------------------------------
Affects Version/s: 0.7.0
Request participants: (was: )
Fix Version/s: 0.7.1
Commit details:
ranger-0.7:
Project: http://git-wip-us.apache.org/repos/asf/ranger/repo
Commit: http://git-wip-us.apache.org/repos/asf/ranger/commit/2ae1346e
Tree: http://git-wip-us.apache.org/repos/asf/ranger/tree/2ae1346e
Diff: http://git-wip-us.apache.org/repos/asf/ranger/diff/2ae1346e
Branch: refs/heads/ranger-0.7
Commit: 2ae1346e36853271c531d753408cfc16ce0dfb53
> Add tag attributes to audit log record
> --------------------------------------
>
> Key: RANGER-1535
> URL: https://issues.apache.org/jira/browse/RANGER-1535
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.7.0, 1.0.0
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Fix For: 1.0.0, 0.7.1
>
>
> Currently, in the access audit log record, the tags column is populated when the accessed
resource has any tags associated with it. However, if a tag has any attributes, their values
are not shown in the audit log record. As authorization decision may be based on the attribute-value(s)
as well as tag-type (such as in the case of expiry_date attribute’s value for EXPIRES_ON
tag-type), they too need to be populated and displayed on audit log record.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
|