v2.6 Improved Error and Requirements Checking and Security

Added boundary checking for variables. Added requirements.txt document for new installations to load required python modules. Also, removed requirement explicitly providing passwords. Now, if a password is not provided, the user will be prompted for the password and the characters will be hidden when entered.

Release 2.5.4 (Refined Bearer Token Timeout Protections - time-based)

Updated release to improves time-based bearer token refresh.

Release 2.5.3 (Bearer Token Timeout Protections - timebased)

Minor adjustments. Removed necessary imports and added DST bearer token timeout protections. This method uses a time-based refresh method. It updates the bearer token ever 275 seconds (before the 300 bearer token expiry).

Release 2.5.2 (Bearer Token Timeout Protections - iteration based)

Minor adjustments. Removed necessary imports and added DST bearer token timeout protections. This method uses an iterative process. New bearer tokens are retrieve from the destination for every 100 key objects that are retrieved.

Release v2.5.1 (Secrets with improved Key Usage and Meta Data Mapping)

In addition to the Secrets capability of v2.5, this minor release improves the mapping of the meta data from source to destination as well as the mapping of key usage data (which is stored in different formats between source and destination.

Furthermore, the NetApp filtering is now applicable to both the source and the destination.

Release v2.5 (Secrets)

Augmented the software so that Secret Objects, in additional to Key Objects, can be retrieved from the source and stored in the destination (-includeSecrets flag required).

Release v2.4.1 (KMIP Client Granularity)

Similar to v2.4, but introduced backward-compatibility with older source servers and their older JSON structures that define object counts, key types, and key counts.

Release v2.4 (KMIP Client Granularity)

With this release, a number of additional parameters have been introduced to support better management of key selection based on the Clients that have been defined in the source server. More specifically, the uses can now ask for a list of Clients and will receive a complete list and an indication of the presence and quantity of symmetric keys contained within each of them. You can also ask for keys for a specific KMIP client.

Furthermore, the user can filter to see key material from a specific Client. This allows greater precision in extracting key material that is more just one Client.

Lastly, to overcome a limitation in key collection where a Client has no user/owner assigned to it, an additional flag is available (-resolveSrcClientOwnership) that temporarily adds the Source Owner to the ownership of the client for the purposes of completing the key collection and then immediately restores the ownership to its original settings.

Release v2.3 (Destination Group Name)

With this release, the user may specify a Destination Group Name. When supplied, keys written to the destination are also accessible by members of the group. If the group does not originally exist, it is created and the dstUser is automatically added to the group on the destination server.

Release v2.2 (NetApp Filtering)

Introduced new filtering capabilities for NetApp keys. These filters allow the utility to copy NetApp keys based on the Custom Attributes of NetApp Node ID, Cluster Name, VserverID, or any combination thereof. Note that the strings supplied to the filters do not need to be complete. For example, if you specify a Node ID of "B2", the filter will process all keys that contain "B2" in the Node ID value.

These filtering capabilities on inclusive of the existing filtering capabilities on UUID.