Releases: strongdm/strongdm-sdk-python
Releases · strongdm/strongdm-sdk-python
v15.10.0
v15.10.0 - Release Entra ID Resource
- Adds support for Microsoft Entra ID
v15.9.0
v15.9.0 - Adjust CLI parameter for Azure MySQL (Managed Identity) driver
- adjusts CLI parameter for Azure MySQL (Managed Identity) to reflect Admin UI field
v15.8.0
v15.8.0 - Support for Managed Identity authentication in MySQL
- adds support for Azure Managed Identity authentication in MySQL
v15.7.0
v15.7.0 - Support new automatic IP allocation modes for Resource bind interfacae
- When creating or updating Resources, the bind interface may now be set to either a specific IP address or one of the defined ResourceIPAllocationMode constants to automatically allocate an IP address from the specified mode (organization default, configured VNM subnet, or configured loopback range). If the bind interface is left empty resources continue to be allocated from the default range, as before.
v15.6.0
v15.6.0 - Added SID field for full enforcement mode in RDP
- Full Enforcement Mode requires certificates in Active Directory to specific a Security Identifier (SID) for all users (UPN). For leased credential RDP resources, this enables the capability to specificy the SID directly.
v15.5.0
v15.5.0 - Add ForceDelete call to forcefully delete managed secret
- Add ForceDelete method for managed secret deletion, that will ignore external system errors like missing ActiveDirectory account or Secret Store error and will delete the secret from the system. This may leave data in the backing Secret Store.
v15.4.0
v15.4.0 - Add AMQP driver that supports the AMQP 0.9.1 and 1.0.0 protocol
v15.2.0
v15.2.0 - Update organization object
- The organization will now hold all of its logging configuration settings in a nested log_config object.
v15.1.0
v15.1.0 - Release Aerospike driver
- The Aerospike driver is now stable and generally available.
v15.0.0
v15.0.0 - Remove Workflow Assignments and Workflow Assignments History Services
- We are removing the workflow assignments and workflow assignments history services due to low utilization and server-side design changes
- Older versions of the SDK will no longer be able to use these services
- Admins can still determine what resources are attached to each workflow by examining the access rules for that workflow