You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/08/01 01:57:55 UTC

[GitHub] [pulsar] complone edited a comment on pull request #10969: [Broker]support ranger

complone edited a comment on pull request #10969:
URL: https://github.com/apache/pulsar/pull/10969#issuecomment-890431892


   @ltamber 
   
   https://github.com/aries-demos/dataops/tree/master/stack-hooks/before-INSTALL/scripts/ranger
   
   The following example illustrates the following scenario
   
   > solved problem
   
   Unified authority control for hdfs, yarn, hive, spark, hbase, storm, kafka, atlas, solr, etc.
   Managed data flow
       - ```ranger-admin``` is responsible for strategy storage and provision of http restful api extensions to provide strategy and modification services
       - ```ranger-usersync``` focuses on synchronizing user and user group data from ldap to ranger
       - ```ranger-tagsync``` is responsible for synchronizing the tags on the atlas to ranger
   > Data flow of the plug-in
      - After the plug-in is allowed, http periodically (30 seconds by default) downloads the policy from ranger-admin to the local /etc/ranger
       - Through the parsing strategy, it is similar to a big hashmap. When the request comes, filter (checkPermission) for permission control
       - The result log is written back to solr, hdfs (the new version of kafka is not enabled)
   
   
   *Pulsar is also here as a component that requires permission verification. Maybe you can synchronize the tags marked by Pulsar on Atlas to ranger based on ranger-tagsync?*


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org