Hanish, this is a good suggestion.

Can you try creating an authorization plugin and just use it for Audit? I
think, most of the pieces would be the same, e.g. Operation, resource,
action, etc. I think, by adding just one more interface exclusively for
audit might make our implementation easy.

Madhan, can you share your thoughts on this?

Thanks

Bosco


From:  Hanish Bansal <[email protected]>
Reply-To:  "[email protected]"
<[email protected]>
Date:  Tuesday, April 14, 2015 at 7:40 AM
To:  "[email protected]" <[email protected]>
Subject:  Reg: Custom Audit functionality

> ​Hi All,
> 
> 
> 
> We want to use Audit capabilities of Apache Ranger for one of our framework.
> Is it possible to log the audits through Ranger using any of the REST API?
> 
> 
> 
> If currently it is not possible, could we develop a pluggable framework for
> auditing so that any application could define its own entities to Audit? That
> would be an excellent feature.
> 
> 
> 
> As an example, we have an entity "profile" and we want to log any updates and
> audit information for profile by defining the entity name and other required
> audit information. We want to see something like below on Ranger UI for other
> entities:
> 
> 
> 
> 
> ​Operation    
> 
> ​Audit Type    ​
> ​User    
> ​Date    
> ​Actions
> ​Session Id
> ​profile updated​ /username
> ​Profile
> ​kate    
> ​04/08/2015 02:41:08 PM
> ​Update
> ​3555
> 
> 
> 
> Please let me know your thoughts on this.
> 
> 
> 
> 
> -------
> Thanks & Regards,
> Hanish Bansal
> 
> 
> 
> 
> 
> 
> 
> 
> NOTE: This message may contain information that is confidential, proprietary,
> privileged or otherwise protected by law. The message is intended solely for
> the named addressee. If received in error, please destroy and notify the
> sender. Any use of this email is prohibited when received in error. Impetus
> does not represent, warrant and/or guarantee, that the integrity of this
> communication has been maintained nor that the communication is free of
> errors, virus, interception or interference.
> 

Reply via email to