Skip to content

RANGER-5399: Ranger: HTTP 403 - User '' lacks delegated-admin privile… #731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Sanket-Shelar wants to merge 1 commit into from
Closed

RANGER-5399: Ranger: HTTP 403 - User '' lacks delegated-admin privile… #731

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3220,16 +3220,16 @@ void ensureAdminAccess(RangerPolicy policy, String grantor) {
final boolean isAdmin;
final boolean isKeyAdmin;

if (StringUtils.isEmpty(grantor)) {
userName = bizUtil.getCurrentUserLoginId();
isAdmin = bizUtil.isAdmin();
isKeyAdmin = bizUtil.isKeyAdmin();
} else {
if (StringUtils.isEmpty(bizUtil.getCurrentUserLoginId()) && StringUtils.isNotEmpty(grantor)) {
Copy link
Contributor

@mneethiraj mneethiraj Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will result in using service account identity (impala/hive/hbase) to authorize grant/revoke calls, which is not correct.

grant/revoke calls by services like Impala/HiveServer2/HBase authenticate with Ranger admin using their service account. The identity of the user entering grant/revoke statement is sent in grantor field of the payload. Ranger admin ensures that the grantor user has necessary privileages to perform the grant/revoke call. If the grantor user doesn't have privileges, the grant/revoke must fail. This is the correct behavior.

Collection<String> userRoles = userMgrGrantor.getRolesByLoginId(grantor);

userName = grantor;
isAdmin = userRoles.contains(RangerConstants.ROLE_SYS_ADMIN);
isKeyAdmin = userRoles.contains(RangerConstants.ROLE_KEY_ADMIN);
} else {
userName = bizUtil.getCurrentUserLoginId();
isAdmin = bizUtil.isAdmin();
isKeyAdmin = bizUtil.isKeyAdmin();
}
boolean isSvcAdmin = isAdmin || svcStore.isServiceAdminUser(policy.getService(), userName);

Expand Down