You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by GitBox <gi...@apache.org> on 2019/06/10 04:25:03 UTC

[GitHub] [atlas] mneethiraj commented on issue #58: [ATLAS-3261] Set kafka user as current principal for Ranger Authorization

mneethiraj commented on issue #58: [ATLAS-3261] Set kafka user as current principal for Ranger Authorization
URL: https://github.com/apache/atlas/pull/58#issuecomment-500287485
 
 
   @arempter - I agree that authorizing based on username in the message can provide an additional layer of control. Given that authentication for each message is likely to add a sizable overhead, I would suggest to make this additional, per-message, authorization an option - controlled via a configuration like "atlas.notification.authorize.using.message.user". This will help avoid the overhead for deployments that don't need this additional layer of authorization control.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services