Skip to content

Dr 1276 upload file attr content - #2373

Draft
mfordkeeper wants to merge 12 commits into
releasefrom
DR-1276-upload-file-attr-content
Draft

mfordkeeper wants to merge 12 commits into
releasefrom
DR-1276-upload-file-attr-content

Conversation

@mfordkeeper

Copy link
Copy Markdown
Contributor

No description provided.

lthievenaz-keeper and others added 12 commits September 10, 2026 09:20
…ser permissions (#2347) (#2359)

* Prevent delegated admin privilege escalation by checking user permissions before granting transfer_account, manage_teams, manage_companies, etc.

* Fix cascade privilege bug, batch error handling (return→continue), enforce removal restriction, case-insensitive usernames, extract helpers and constants

* Reuse get_user_root_nodes for root-admin check, gate privilege removal

Root-admin detection for require_account_share now reuses EnterpriseCommand.get_user_root_nodes() (bitmask-based root identification) instead of a bespoke parent_id walk, avoiding drift from the existing vetted implementation. Privilege authorization check now also gates removal, not just grants, since a node admin without transfer_account/manage_teams/manage_companies could otherwise strip those privileges from a role that depends on them. Added tests for manage_companies denial and removal authorization (denied/allowed).
…ndows (#2361) (#2366)

* Fix background service mode and ngrok breaking in windows

* Change tunnel logs save directory

* Refactor and error handling for ngrok

* Fix copilot review points

* Fix claude review points

* Fix test cases

* Fix review comments

* Fix review comments
…2353) (#2364)

* Enforce allow_pam_gateway policy on pam gateway new/remove

Commander let any user create and delete PAM Gateways via pam gateway
new/remove regardless of their role's "Can create, deploy, and manage
Keeper Gateways" enforcement policy, since the commands only checked
KSM Application record access, not the gateway-specific enforcement
flag. Mirrors the existing PAM tunnel/connection/rotation enforcement
gates using the shared is_pam_action_allowed_by_enforcement helper.
Also patched the legacy discoveryrotation_v1 commands, reachable via
pam legacy, to close the same bypass there.

* Add legacy PAM gateway test coverage, dedupe enforcement check

* Add mixed-permission test coverage for PAM gateway enforcement
* Very first cut at adding HashiCorp PAM config support.

* Renamed pamHashiCorpVaultConfiguration to pamHashiCorpConfiguration.

* Added pamHashiCorpId configuration attribute.

* Finished support for hashicorp-id attribute.
…and record-update (#2362) (#2369)

* Fix security issue exposing sensitive data from bankAccount, bankCard, sshKeys,
softwareLicense, and encryptedNotes records in Docker logs during record-add
and record-update operations.

- Add protobuf JSON sanitization to mask sensitive fields in DEBUG logs
- Enhance service API logging patterns to cover prefixed field formats
- Add 17 comprehensive unit and integration tests

Sensitive values now masked with *** at both protobuf and service API layers.

* Add licenseNumber and encryptedNote masking; add comprehensive logging tests for all command formats

* Consolidate sanitization logic into shared module with custom field label patterns

* updated test file with correct import

* fixed incorrect fucntion call

* removed duplicate SENSITIVE_FIELD_TYPES, removed redundant if/else and updated copyright year and contact email

* removed login field from the sensitive field types since it's just the username and is already visible in the vault

* Removed the email sanitization pattern

* removed encryption for --notes values

* Add note field masking for encryptedNotes records
@mfordkeeper
mfordkeeper marked this pull request as draft September 17, 2026 17:51
@mfordkeeper
mfordkeeper changed the base branch from master to release September 17, 2026 17:51

This branch has not been deployed

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

8 participants