Skip to content

Conversation

@sbernauer
Copy link
Member

This reverts commit e6d2d60.

Description

Reverting the change, as this introduced the following security risk:

Imagine the situation the user hbase/hbase-prod.prod-namespace.svc.cluster.local@CLUSTER.LOCAL access HDFS, the GroupMapper will be asked for the groups of the user hbase and returns the groups ["prod"]. This response will be cached by HDFS by the key hbase. If a different user hbase/hbase-dev.dev-namespace.svc.cluster.local@CLUSTER.LOCAL accesses HDFS a few seconds later the mapping hbase -> ["prod"] is still cached and HDFS will falsely assume the hbase-dev HBase is in the prod group!

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes
# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
# Acceptance
- [ ] Proper release label has been added

@sbernauer sbernauer added this pull request to the merge queue Feb 27, 2024
Merged via the queue into main with commit a2b7ece Feb 27, 2024
@sbernauer sbernauer deleted the fix/revert-mapper-long-name branch February 27, 2024 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants