[
https://issues.apache.org/jira/browse/ATLAS-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated ATLAS-4831:
------------------------------------
Description:
Atlas + Ranger + Active Directory / LDAP Integration:
Issue is with AD Group Sync in Atlas.
When a user is added to the AD group. Permissions are set to AD groups.
In this case ideally, Atlas should allow the User (Because user is added to the
AD Group) to interact with Atlas perform Read & Write operations.
But the User is not able to perform the Read & Write operations and getting
Unauthorized User Exception with 401 error code.
I searched this ticket https://issues.apache.org/jira/browse/ATLAS-4357
Any alternate or work around approach for this if not direct solution
was:
Atlas + Ranger + Active Directory / LDAP Integration:
Issue is with AD Group Sync in Atlas.
When a user is added to the AD group. Permissions are set to AD groups.
In this case ideally, Atlas should allow the User (Because user is added to the
AD Group) to interact with Atlas perform Read & Write operations.
But the User is not able to perform the Read & Write operations and getting
Unauthorized User Exception with 401 error code.
> Issue is with AD Group Sync in Atlas
> ------------------------------------
>
> Key: ATLAS-4831
> URL: https://issues.apache.org/jira/browse/ATLAS-4831
> Project: Atlas
> Issue Type: Bug
> Reporter: Jagadesh Kiran N
> Priority: Blocker
>
> Atlas + Ranger + Active Directory / LDAP Integration:
> Issue is with AD Group Sync in Atlas.
> When a user is added to the AD group. Permissions are set to AD groups.
> In this case ideally, Atlas should allow the User (Because user is added to
> the AD Group) to interact with Atlas perform Read & Write operations.
> But the User is not able to perform the Read & Write operations and getting
> Unauthorized User Exception with 401 error code.
>
> I searched this ticket https://issues.apache.org/jira/browse/ATLAS-4357
>
> Any alternate or work around approach for this if not direct solution
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
