Skip to content

Support empty user/ports and other improvements#2122

Merged
sk-keeper merged 2 commits into
Keeper-Security:releasefrom
lthievenaz-keeper:update-kcm-import
Jun 13, 2026
Merged

Support empty user/ports and other improvements#2122
sk-keeper merged 2 commits into
Keeper-Security:releasefrom
lthievenaz-keeper:update-kcm-import

Conversation

@lthievenaz-keeper

Copy link
Copy Markdown
Contributor
  • If a KCM connection has no user, the export will log the record for future process.
  • If a KCM connection has no port, it will default to the port mapping defined in KCM_mappings.json
  • Fixed a duplication issue of SFTP parameters caused by a reference error.
  • Set the autodocker docker-file location as default
  • Reworked how logged records are displayed on output file.

If connection has empty port, it will default to the ports defined in this file (can be customized for custom default ports)
Also added new parameter allow-file-uploads for RBI
If a KCM connection has no user, the export will log the record for future process.
If a KCM connection has no port, it will default to the port mapping defined in KCM_mappings.json
Fixed a duplication issue of SFTP parameters caused by a reference error.
Set the autodocker docker-file location as default
Reworked how logged records are displayed on output file.
@lthievenaz-keeper
lthievenaz-keeper changed the base branch from master to release June 5, 2026 11:52
@sk-keeper
sk-keeper force-pushed the release branch 3 times, most recently from b11acff to c6ec45e Compare June 13, 2026 02:41
@sk-keeper
sk-keeper merged commit ab6267f into Keeper-Security:release Jun 13, 2026
6 checks passed
sk-keeper pushed a commit that referenced this pull request Jun 23, 2026
* Add support for port mapping

If connection has empty port, it will default to the ports defined in this file (can be customized for custom default ports)
Also added new parameter allow-file-uploads for RBI

* Support empty user/ports and other improvements

If a KCM connection has no user, the export will log the record for future process.
If a KCM connection has no port, it will default to the port mapping defined in KCM_mappings.json
Fixed a duplication issue of SFTP parameters caused by a reference error.
Set the autodocker docker-file location as default
Reworked how logged records are displayed on output file.
jpkeepersecurity pushed a commit that referenced this pull request Jul 3, 2026
* Add support for port mapping

If connection has empty port, it will default to the ports defined in this file (can be customized for custom default ports)
Also added new parameter allow-file-uploads for RBI

* Support empty user/ports and other improvements

If a KCM connection has no user, the export will log the record for future process.
If a KCM connection has no port, it will default to the port mapping defined in KCM_mappings.json
Fixed a duplication issue of SFTP parameters caused by a reference error.
Set the autodocker docker-file location as default
Reworked how logged records are displayed on output file.
pvagare-ks pushed a commit that referenced this pull request Jul 16, 2026
* Add support for port mapping

If connection has empty port, it will default to the ports defined in this file (can be customized for custom default ports)
Also added new parameter allow-file-uploads for RBI

* Support empty user/ports and other improvements

If a KCM connection has no user, the export will log the record for future process.
If a KCM connection has no port, it will default to the port mapping defined in KCM_mappings.json
Fixed a duplication issue of SFTP parameters caused by a reference error.
Set the autodocker docker-file location as default
Reworked how logged records are displayed on output file.
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