[jira] [Updated] (RANGER-3697) Migrate all python scripts in Ranger to Python3
[ https://issues.apache.org/jira/browse/RANGER-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-3697: --- Due Date: 30/Dec/22 (was: 20/Dec/22) > Migrate all python scripts in Ranger to Python3 > --- > > Key: RANGER-3697 > URL: https://issues.apache.org/jira/browse/RANGER-3697 > Project: Ranger > Issue Type: Improvement > Components: admin, Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > > Python 2 has sunset as of Jan 1, 2020. All scripts using python2 should > eventually move to python3. > Python2 will no longer be supported, ranger 3.0 and onwards. > Article: > [https://www.python.org/doc/sunset-python-2/#:~:text=We%20have%20decided%20that%20January,as%20soon%20as%20you%20can.] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4025) Ranger improvement - Roles Import/export API for ranger admin
Dineshkumar Yadav created RANGER-4025: - Summary: Ranger improvement - Roles Import/export API for ranger admin Key: RANGER-4025 URL: https://issues.apache.org/jira/browse/RANGER-4025 Project: Ranger Issue Type: New Feature Components: Ranger Reporter: Dineshkumar Yadav Assignee: Dineshkumar Yadav Provide API for Roles import/export. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4024) Adding requestId as part of Ranger logs via RangerMDCFilter when the request header contains request-Id
[
https://issues.apache.org/jira/browse/RANGER-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran updated RANGER-4024:
-
Flags: Patch
> Adding requestId as part of Ranger logs via RangerMDCFilter when the request
> header contains request-Id
> ---
>
> Key: RANGER-4024
> URL: https://issues.apache.org/jira/browse/RANGER-4024
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.3.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Labels: patch-available
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4024-Adding-requestId-as-part-of-Ranger-logs-.patch
>
>
> In Ranger, we do not have the correlation Id which needs to be stored in the
> logs whenever we get the requestId header from the caller microservice
> Proposal:
> RangerMDCFilter will capture the correlation Id which needs to be stored in
> the logs whenever we get the requestId header from the caller microservice
> This RangerMDCFilter can be enabled in the web.xml and logging
> ConversionPattern
>
> {code:java}
>
> RangerMDCFilter
>
>
> RangerMDCFilter
> /service/*
> {code}
>
> and to change the conversion pattern to something like this, using the %X{}
> placeholder for each entry contained in the MDC we want to be logged:
> Example:
> {code:java}
> class="ch.qos.logback.core.rolling.RollingFileAppender">
>
> ${logdir}/ranger-admin-${hostname}-${user}.log
> true
>
> %date [%thread] %level{5} [%file:%line]
> [requestId=%X{REQUEST_ID}] %msg%n
>
>
>
> ${logdir}/ranger-admin-${hostname}-${user}.log.%d{-MM-dd}
> 15
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (RANGER-4024) Adding requestId as part of Ranger logs via RangerMDCFilter when the request header contains request-Id
[ https://issues.apache.org/jira/browse/RANGER-4024 ]
Ramachandran deleted comment on RANGER-4024:
--
was (Author: JIRAUSER295265):
[^0001-RANGER-4024-Adding-requestId-as-part-of-Ranger-logs-.patch]
> Adding requestId as part of Ranger logs via RangerMDCFilter when the request
> header contains request-Id
> ---
>
> Key: RANGER-4024
> URL: https://issues.apache.org/jira/browse/RANGER-4024
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.3.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Labels: patch-available
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4024-Adding-requestId-as-part-of-Ranger-logs-.patch
>
>
> In Ranger, we do not have the correlation Id which needs to be stored in the
> logs whenever we get the requestId header from the caller microservice
> Proposal:
> RangerMDCFilter will capture the correlation Id which needs to be stored in
> the logs whenever we get the requestId header from the caller microservice
> This RangerMDCFilter can be enabled in the web.xml and logging
> ConversionPattern
>
> {code:java}
>
> RangerMDCFilter
>
>
> RangerMDCFilter
> /service/*
> {code}
>
> and to change the conversion pattern to something like this, using the %X{}
> placeholder for each entry contained in the MDC we want to be logged:
> Example:
> {code:java}
> class="ch.qos.logback.core.rolling.RollingFileAppender">
>
> ${logdir}/ranger-admin-${hostname}-${user}.log
> true
>
> %date [%thread] %level{5} [%file:%line]
> [requestId=%X{REQUEST_ID}] %msg%n
>
>
>
> ${logdir}/ranger-admin-${hostname}-${user}.log.%d{-MM-dd}
> 15
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3537) Find a viable replacement of Backbone JS for Ranger UI.
[ https://issues.apache.org/jira/browse/RANGER-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-3537: --- Attachment: 0004-RANGER-3537.patch > Find a viable replacement of Backbone JS for Ranger UI. > --- > > Key: RANGER-3537 > URL: https://issues.apache.org/jira/browse/RANGER-3537 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-3537.patch, 0002-RANGER-3537.patch, > 0003-RANGER-3537.patch, 0004-RANGER-3537.patch > > > As backbone JS is an old library, and backbone js related library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 5 years, we need to move to the latest and stable UI framework > for Ranger UI. This is critical for security reasons. > Research for a viable replacement of Backbone JS for Ranger UI. > So we are planning to move Ranger UI code base to react js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74246: RANGER-3537 : Find a viable replacement of Backbone JS for Ranger UI.
> On Dec. 15, 2022, 9:30 p.m., Madhan Neethiraj wrote: > > Dhaval - the fixes look good. Thank you for the quick turnaround. > > > > Can you please look into following issues as well? > > 1. While trying to create a policy in Atlas service, 'Type Category' is the > > default resource shown. Following list is shown for values: classification, > > enum, enity, relationship, struct, businessmetadata. After changing the > > resource to any other type, Entity Type/Atlas Service/Relationship Type, > > the same dropdown list is shown for values. This doesn't look correct. > > > > 2. List of values for 'Type Category/Type Name' has entries with value > > _NOT_CLASSIFIED. This doesn't look correct. Hi madhan, Updated the patch with the latest changes that address atlas service policy displaying the wrong default value in "Entity type". - Dhaval --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74246/#review225003 --- On Dec. 15, 2022, 1:03 p.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74246/ > --- > > (Updated Dec. 15, 2022, 1:03 p.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Brijesh Bhalala, > Dhaval Shah, Dineshkumar Yadav, Gautam Borad, Harshal Chavan, jay zalavadia, > Jayendra Parab, Kishore Gopalakrishna, Abhay Kulkarni, Madhan Neethiraj, > Mahesh Bandal, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, Nitin Galave, > Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-3537 > https://issues.apache.org/jira/browse/RANGER-3537 > > > Repository: ranger > > > Description > --- > > As backbone JS is an old library, and its related js library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 6 years. Therefore we need to move to the latest and stable UI > framework for Ranger UI. This is critical for security reasons. > > The given review request contains code changes for migrating Ranger Admin UI > to use React JS. > Created a react-webapp directory inside the existing webapp directory to add > the code changes. > > To build a Ranger Admin UI with this changes, please use below mvn command : > > --> mvn clean compile package -DskipTests -Psecurity-admin-react > > > Diffs > - > > security-admin/pom.xml f887e03a1 > security-admin/src/main/resources/conf.dist/security-applicationContext.xml > 4ee80b98f > security-admin/src/main/webapp/react-webapp/README.md PRE-CREATION > security-admin/src/main/webapp/react-webapp/babel.config.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/paths.js PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.dev.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.prod.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/package-lock.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/package.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/src/App.jsx PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/CommonComponents.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/CreatableField.jsx > PRE-CREATION > security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/XATableLayout.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/main.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/calendar.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/date_input.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/datepicker.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/popover.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/keyevent.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/react-typeahead.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/tokenizer/index.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/s
Re: Review Request 74246: RANGER-3537 : Find a viable replacement of Backbone JS for Ranger UI.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74246/ --- (Updated Dec. 21, 2022, 2:07 p.m.) Review request for ranger, Ankita Sinha, Don Bosco Durai, Brijesh Bhalala, Dhaval Shah, Dineshkumar Yadav, Gautam Borad, Harshal Chavan, jay zalavadia, Jayendra Parab, Kishore Gopalakrishna, Abhay Kulkarni, Madhan Neethiraj, Mahesh Bandal, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, Nitin Galave, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-3537 https://issues.apache.org/jira/browse/RANGER-3537 Repository: ranger Description --- As backbone JS is an old library, and its related js library like backbone-form, backbone-pagination, and backbone table has not been updated for the last 6 years. Therefore we need to move to the latest and stable UI framework for Ranger UI. This is critical for security reasons. The given review request contains code changes for migrating Ranger Admin UI to use React JS. Created a react-webapp directory inside the existing webapp directory to add the code changes. To build a Ranger Admin UI with this changes, please use below mvn command : --> mvn clean compile package -DskipTests -Psecurity-admin-react Diffs (updated) - security-admin/pom.xml f887e03a1 security-admin/src/main/resources/conf.dist/security-applicationContext.xml 4ee80b98f security-admin/src/main/webapp/react-webapp/README.md PRE-CREATION security-admin/src/main/webapp/react-webapp/babel.config.json PRE-CREATION security-admin/src/main/webapp/react-webapp/config/paths.js PRE-CREATION security-admin/src/main/webapp/react-webapp/config/webpack.config.js PRE-CREATION security-admin/src/main/webapp/react-webapp/config/webpack.dev.config.js PRE-CREATION security-admin/src/main/webapp/react-webapp/config/webpack.prod.config.js PRE-CREATION security-admin/src/main/webapp/react-webapp/package-lock.json PRE-CREATION security-admin/src/main/webapp/react-webapp/package.json PRE-CREATION security-admin/src/main/webapp/react-webapp/src/App.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/CommonComponents.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/CreatableField.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/XATableLayout.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/main.jsx PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/calendar.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/date_input.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/datepicker.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/popover.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/keyevent.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/react-typeahead.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/tokenizer/index.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/tokenizer/token.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/typeahead/index.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/typeahead/option.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/typeahead/selector.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/hooks/usePrompt.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/hooks/withRouter.js PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/cancel_search.png PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/defult_zone.png PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/error-404-icon.png PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/favicon.ico PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/folder-grey.png PRE-CREATION security-admin/src/main/webapp/react-webapp/src/images/ranger_logo.png PRE-CREATION security-admin/src/main/webapp/react-webapp/src/index.html PRE-CREATION security-admin/src/main/webapp/react-webapp/src/index.jsx PRE-CREATION security-admin/src/m
[jira] [Commented] (RANGER-3896) Update Ozone dependency version to latest 1.3.0
[ https://issues.apache.org/jira/browse/RANGER-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650923#comment-17650923 ] Neil Joshi commented on RANGER-3896: Thanks [~rmani] - I've updated the Review request adding the group to the request.(y) > Update Ozone dependency version to latest 1.3.0 > --- > > Key: RANGER-3896 > URL: https://issues.apache.org/jira/browse/RANGER-3896 > Project: Ranger > Issue Type: Bug > Components: plugins, Ranger >Reporter: Neil Joshi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > update Ozone dependency in pom build file from 1.0.0 to latest Ozone version > 1.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74255: RANGER-3978: Docker setup fixes - incorrect mysql path in KMS, incorrect service-config
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74255/#review225019 --- Ship it! Ship It! - Selvamohan Neethiraj On Dec. 15, 2022, 4:14 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74255/ > --- > > (Updated Dec. 15, 2022, 4:14 p.m.) > > > Review request for ranger, Abhay Kulkarni, Ramesh Mani, and Selvamohan > Neethiraj. > > > Repository: ranger > > > Description > --- > > updated Docker setup to fix the following: > - updated version of HBase and Kafka to be in sync with pom.xml > - fixed docker build image to recognize PROFILE in .env > - incorrect mysql path in KMS setup > - updated READMe.md to include KMS in docker command to build and run > - incorrect service config for Hive, HBase and Knox services > > > Diffs > - > > dev-support/ranger-docker/.env 020798132 > dev-support/ranger-docker/Dockerfile.ranger-kms 4cf8b9d73 > dev-support/ranger-docker/README.md e18b0e7ff > dev-support/ranger-docker/docker-compose.ranger-build.yml f0b5b05e0 > dev-support/ranger-docker/scripts/create-ranger-services.py 1b2bcafd2 > > > Diff: https://reviews.apache.org/r/74255/diff/2/ > > > Testing > --- > > verified that docker build completes successfully and services startup > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 74246: RANGER-3537 : Find a viable replacement of Backbone JS for Ranger UI.
> On Dec. 15, 2022, 9:30 p.m., Madhan Neethiraj wrote: > > Dhaval - the fixes look good. Thank you for the quick turnaround. > > > > Can you please look into following issues as well? > > 1. While trying to create a policy in Atlas service, 'Type Category' is the > > default resource shown. Following list is shown for values: classification, > > enum, enity, relationship, struct, businessmetadata. After changing the > > resource to any other type, Entity Type/Atlas Service/Relationship Type, > > the same dropdown list is shown for values. This doesn't look correct. > > > > 2. List of values for 'Type Category/Type Name' has entries with value > > _NOT_CLASSIFIED. This doesn't look correct. > > Dhaval Rajpara wrote: > Hi madhan, > > Updated the patch with the latest changes that address atlas service > policy displaying the wrong default value in "Entity type". Dhaval - the fix in Atlas policy UI is good! Build with security-admin-react profile generates large number of files under security-admin/src/main/webapp/react-webapp/node_modules/. Can these files be generated under target directory? - Madhan --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74246/#review225003 --- On Dec. 21, 2022, 2:07 p.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74246/ > --- > > (Updated Dec. 21, 2022, 2:07 p.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Brijesh Bhalala, > Dhaval Shah, Dineshkumar Yadav, Gautam Borad, Harshal Chavan, jay zalavadia, > Jayendra Parab, Kishore Gopalakrishna, Abhay Kulkarni, Madhan Neethiraj, > Mahesh Bandal, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, Nitin Galave, > Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-3537 > https://issues.apache.org/jira/browse/RANGER-3537 > > > Repository: ranger > > > Description > --- > > As backbone JS is an old library, and its related js library like > backbone-form, backbone-pagination, and backbone table has not been updated > for the last 6 years. Therefore we need to move to the latest and stable UI > framework for Ranger UI. This is critical for security reasons. > > The given review request contains code changes for migrating Ranger Admin UI > to use React JS. > Created a react-webapp directory inside the existing webapp directory to add > the code changes. > > To build a Ranger Admin UI with this changes, please use below mvn command : > > --> mvn clean compile package -DskipTests -Psecurity-admin-react > > > Diffs > - > > security-admin/pom.xml f887e03a1 > security-admin/src/main/resources/conf.dist/security-applicationContext.xml > 4ee80b98f > security-admin/src/main/webapp/react-webapp/README.md PRE-CREATION > security-admin/src/main/webapp/react-webapp/babel.config.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/paths.js PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.dev.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/config/webpack.prod.config.js > PRE-CREATION > security-admin/src/main/webapp/react-webapp/package-lock.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/package.json PRE-CREATION > security-admin/src/main/webapp/react-webapp/src/App.jsx PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/CommonComponents.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/CreatableField.jsx > PRE-CREATION > security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/XATableLayout.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/main.jsx > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/calendar.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/date_input.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/datepicker.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-datepicker/popover.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src/components/structured-filter/react-typeahead/keyevent.js > PRE-CREATION > > security-admin/src/main/webapp/react-webapp/src
Re: Review Request 74255: RANGER-3978: Docker setup fixes - incorrect mysql path in KMS, incorrect service-config
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74255/ --- (Updated Dec. 21, 2022, 8:04 p.m.) Review request for ranger, Abhay Kulkarni, Ramesh Mani, and Selvamohan Neethiraj. Changes --- updated README.md for recent changes in docker build - to set environment variables DOCKER_BUILDKIT and COMPOSE_DOCKER_CLI_BUILD Repository: ranger Description --- updated Docker setup to fix the following: - updated version of HBase and Kafka to be in sync with pom.xml - fixed docker build image to recognize PROFILE in .env - incorrect mysql path in KMS setup - updated READMe.md to include KMS in docker command to build and run - incorrect service config for Hive, HBase and Knox services Diffs (updated) - dev-support/ranger-docker/.env 020798132 dev-support/ranger-docker/Dockerfile.ranger-kms 4cf8b9d73 dev-support/ranger-docker/README.md e18b0e7ff dev-support/ranger-docker/docker-compose.ranger-build.yml 700bdc630 dev-support/ranger-docker/scripts/create-ranger-services.py 1b2bcafd2 Diff: https://reviews.apache.org/r/74255/diff/3/ Changes: https://reviews.apache.org/r/74255/diff/2-3/ Testing --- verified that docker build completes successfully and services startup Thanks, Madhan Neethiraj
[jira] [Created] (RANGER-4026) Provide option to update group memberships when same users/groups are synced from different sync sources
Sailaja Polavarapu created RANGER-4026: -- Summary: Provide option to update group memberships when same users/groups are synced from different sync sources Key: RANGER-4026 URL: https://issues.apache.org/jira/browse/RANGER-4026 Project: Ranger Issue Type: Improvement Components: usersync Reporter: Sailaja Polavarapu RANGER-3254 implemented a change in user/group mapping so that sync source is taken into account when a group name matches multiple sources. LDAP users belonging to a group like "CN=mygroup" will not be synced in Ranger if there is an existing "mygroup" that was imported by UnixUserGroupBuilder. This breaks a very common use case where posix users and groups are synced to the OS from an LDAP backend using SSSD, Centrify, or similar utilities. In those cases, both the linux OS and LDAP/AD are using the same identity repository. If Ranger imported a set of users and groups from one sync source, and then later switches to another, group mappings break and users don't get all of their groups. Provide an option for customers to treat users/groups from multiple sync sources as same for updating group memberships. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4026) Provide option to update group memberships when same users/groups are synced from different sync sources
[ https://issues.apache.org/jira/browse/RANGER-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Polavarapu reassigned RANGER-4026: -- Assignee: Sailaja Polavarapu > Provide option to update group memberships when same users/groups are synced > from different sync sources > > > Key: RANGER-4026 > URL: https://issues.apache.org/jira/browse/RANGER-4026 > Project: Ranger > Issue Type: Improvement > Components: usersync >Reporter: Sailaja Polavarapu >Assignee: Sailaja Polavarapu >Priority: Major > > RANGER-3254 implemented a change in user/group mapping so that sync source is > taken into account when a group name matches multiple sources. LDAP users > belonging to a group like "CN=mygroup" will not be synced in Ranger if there > is an existing "mygroup" that was imported by UnixUserGroupBuilder. > This breaks a very common use case where posix users and groups are synced to > the OS from an LDAP backend using SSSD, Centrify, or similar utilities. In > those cases, both the linux OS and LDAP/AD are using the same identity > repository. If Ranger imported a set of users and groups from one sync > source, and then later switches to another, group mappings break and users > don't get all of their groups. > Provide an option for customers to treat users/groups from multiple sync > sources as same for updating group memberships. -- This message was sent by Atlassian Jira (v8.20.10#820010)
