[HBASE-13235] Revisit the security auditing semantics.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0, 2.0.0
• Assignee: Srikanth Srungarapu
• Reporter: Srikanth Srungarapu
• Created: 13/Mar/15 19:19
• Updated: 03/Jun/15 15:29
• Resolved: 19/Mar/15 07:18

Description

More specifically, the following things need a closer look. (Will include more based on feedback and/or suggestions)

• Table name (say test) instead of fully qualified table name(default:test) being used.
• Right now, we're using the scope to be similar to arguments for operation. Would be better to decouple the arguments for operation and scope involved in checking. For e.g. say for createTable, we have the following audit log

  Access denied for user esteban; reason: Insufficient permissions; remote address: /10.20.30.1; request: createTable; context: (user=srikanth@XXX, scope=default, action=CREATE)
  

  The scope was rightly being used as default namespace, but we're missing out the information like operation params for CREATE which we used to log prior to HBASE-12511.

Would love to hear inputs on this!

Issue Links

• links to: reviewboard

Sub-Tasks

• Document the format of audit logs.: Closed