Skip Navigation

Fixed issues

The following issues are fixed in this release:
  • POST /{tenantGuid}/api/v1/users/{userGuid}/accessPasswords did not work as expected when using GENERATE_UNLOCK_ACCESS_KEY and specifying the 
    BlackBerry Dynamics
     unlock key email template guid. (2630492)
  • Using POST /{tenantGuid}/api/v1/users/{userGuid}/accessPasswords to generate an access key resulted in a 500 error if the user did not have an email address, but the error message did not indicate that this was the cause of the error. In this release, the error message has been updated to clarify the cause. (2610594)
  • GET /{tenantGuid}/api/v1/users did not work as expected when using dynamicsContainerId as the query parameter. (2610583)
  • Using PUT /{tenantGuid}/api/v1/users/{userGuid}/profiles/{profileGuid}/certificate to update a certificate for a user credential profile resulted in an ExternalPKIException error if the certificate file was in the wrong format, but the error message did not indicate that this was the cause of the error. In this release, the error message has been updated to clarify the cause and list the supported formats. (2610574)
  • GET /{tenantGuid}/api/v1/users/{userGuid}/userDevices returned devices that were not in the ENROLLED state. (2603382)
  • Previously, you could not override an app package ID for a 
    BlackBerry Dynamics
     application binary. In this release, you can do this using PATCH /{tenantGuid}/api/v1/applications/{appGuid}/{osFamilyName}. (2595974)
  • GET /{tenantGuid}/api/v1/applicationServers did not return the application servers in the Default 
    BlackBerry Dynamics
     connection profile. (2591489)
  • In the profile categories data type, the GOOD_DYNAMICS_CONNECTIVITY and GOOD_DYNAMICS_SECURITY values are removed in this release. As of 
    BlackBerry UEM
     12.9, they have been replaced with BLACKBERRY_DYNAMICS_CONNECTIVITY and BLACKBERRY_DYNAMICS_SECURITY, respectively. (2545019)