Skip to content

Releases: strongdm/strongdm-sdk-java

v12.0.0

08 Jan 19:02
Compare
Choose a tag to compare

v12.0.0 - Clean up invalid permission constants

  • Removes permission constants which either had no effect on the API server at all or were invalid to specify from the SDKs.

v11.23.0

08 Jan 17:15
Compare
Choose a tag to compare

v11.23.0 - Workflow-Level Settings

  • Adds the ability to overide organization level access request duration settings at the workflow level

v11.22.0

07 Jan 04:39
Compare
Choose a tag to compare

v11.22.0 - Add symmetric keys to encrypted RDP replays

v11.21.0

18 Dec 20:24
Compare
Choose a tag to compare

v11.21.0 - Support resource locks for certificate based RDP servers

v11.20.0

27 Nov 16:26
Compare
Choose a tag to compare

v11.20.0 - Access Request Requested and Result Durations

  • Deprecates the duration field on AccessRequests, which was represented in an integer number of seconds
  • Adds two new fields to AccessRequest, RequestedDuration and ResultDuration. Both are duration types.

v11.18.0

08 Nov 21:29
Compare
Choose a tag to compare

v11.18.0 - Add unstable GCP Workforce Identity Federation Drivers

  • This release allows beta users to utilize StrongDM APIs to create
    Resources that utilize GCP's Workforce Identity Federation

v11.17.0

31 Oct 16:56
Compare
Choose a tag to compare

v11.17.0 - Add AWS (Instance Profile) resource type

  • This release adds support for the AWS (Instance Profile) resource type

v11.16.0

30 Oct 21:17
Compare
Choose a tag to compare

v11.16.0 - Bulk Healthcheck Retrieval

  • Adds a new healthchecks service for fetching most recent healthchecks

v11.15.0

14 Oct 16:05
Compare
Choose a tag to compare

v11.15.0 - Mark the SSHPassword resource type as stable

  • This release marks the SSHPassword resource type as stable.

v11.14.0

07 Oct 15:50
Compare
Choose a tag to compare

v11.14.0 - Add Impersonation User and Impersonation Groups to QueryCapture

  • Content
    This release adds Impersonation User and Impersonation Groups fields to the QueryCapture model.

These fields are populated when the client performs user and group impersonation in K8s, i.e. --as user --as-group group.