Skip to content

PAM Project Extend - Add support for stringified JSON#1970

Merged
sk-keeper merged 2 commits intoKeeper-Security:releasefrom
lthievenaz-keeper:pam-extend-accept-stringified-json
Apr 24, 2026
Merged

PAM Project Extend - Add support for stringified JSON#1970
sk-keeper merged 2 commits intoKeeper-Security:releasefrom
lthievenaz-keeper:pam-extend-accept-stringified-json

Conversation

@lthievenaz-keeper
Copy link
Copy Markdown
Contributor

PAM Project Extend command requires physical file with sensitive credential data. This commit adds support for passing stringified JSON data in the filename directly, rather than a filepath.

Command syntax:

CLI

pam project extend -c <config_uid> -f "{\"pam_data\":{\"resources\":[...],\"users\":[...]}

SDK

from keepercommander.commands.pam_import.extend PAMProjectExtendCommand

data = json.dumps(list_records)
PAMProjectExtendCommand().execute(params,config=config_uid, file_name=data)

PAM Project Extend command requires physical file with sensitive credential data.
This commit adds support for passing stringified JSON data in the filename directly, rather than a filepath.
@sk-keeper sk-keeper force-pushed the release branch 2 times, most recently from ccaf00a to 22d8a2d Compare April 24, 2026 18:34
@sk-keeper sk-keeper merged commit edfdbbc into Keeper-Security:release Apr 24, 2026
4 checks passed
sk-keeper pushed a commit that referenced this pull request Apr 24, 2026
* Support passing stringified JSON as filename

PAM Project Extend command requires physical file with sensitive credential data.
This commit adds support for passing stringified JSON data in the filename directly, rather than a filepath.

* Remove debug statement
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