Operational Defect Database
BugZero updated this defect 47 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 95397
Workspace ONE UEM: End of Life of deprecated Workspace One UEM APIs
Last update date:
4/2/2024
Affected products:
Workspace ONE
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Details
Overview The Workspace ONE UEM team is consistently driving to improve and ensure that we are delivering a hardened and secure platform for all UEM customers. As part of delivering on that goal, the UEM team has targeted a large group of the current Workspace ONE UEM APIs with the intent to overall improve our API health. The first major milestone of these changes is targeted at a key component of any API lifecycle, deprecating legacy APIs previously marked for deprecation. These APIs have held deprecated status for a considerable period, and the introduction of newer APIs has brought forth additional security requirements. In line with our commitment to enhancing the performance and security posture of Workspace ONE UEM APIs, we will remove these deprecated APIs and, where applicable, substitute them with improved alternatives. Change We will be removing APIs that have been marked as deprecated, which will render them no longer able to be called or executed by any API integrations or implementations etc. The deprecation status has been previously communicated in our API documentation, indicated by a strikethrough and warning. For these APIs, users should migrate and switch to alternative endpoints. A list of APIs targeted for removal in an upcoming Workspace ONE UEM release (check release notes of upcoming versions for reference), along with the alternative endpoints that you should transition to is noted below: Sr. No.API URI routeMethod typeVersionAlternative API Method typeVersion1/system/users/registereddevices/deletebyassetnumberPOST1/system/users/registereddevices/deletePOST12/system/users/registereddevices/deletebyserialnumberPOST1/system/users/registereddevices/deletePOST13/system/users/registereddevices/deletebyudidPOST1/system/users/registereddevices/deletePOST14/system/groups/{id}/sampleratesbyplatformGET1/system/groups/{id}/sampleratesGET15/mam/apps/public/{applicationid}/statusGET1/mam/apps/public/{id}GET16/mcm/groups/{groupId}/contentgatewayGET1/mcm/V2/groups/{groupId}/contentgatewayGET17/mcm/groups/contentgateway/{contentGatewayConfigurationId}POST1/mcm/V2/groups/contentgateway/{contentGatewayConfigurationUuid}POST18/mdm/picklists/organizationgroups/{ogId}/certificateauthorities/{certificateAuthorityId}/getcertificatetemplatesGET1/mdm/picklists/organizationgroups/{ogid}/certificateauthorities/{certificateAuthorityId}/certificatetemplatesGET19/mdm/devices/macaddress/{macaddress}DELETE1/mdm/devicesDELETE110/mdm/devices/{id}/sendmessagePOST1/mdm/devices/messages/{id}/messagePOST111/mdm/devices/macaddress/{macaddress}/sendmessagePOST1/mdm/devices/messages/messagePOST112/mdm/devices/udid/{udid}/sendmessagePOST1/mdm/devices/messages/messagePOST113/mdm/devices/assetnumber/{assetnumber}/updatecustomattributesPOST1/mdm/devices/assetnumber/{assetnumber}/customattributesPUT114/mdm/scripts/{scriptUuid}/assignments/updaterankingPATCH1mdm/scripts/{scriptUuid}/updateassignmentsPOST115/mdm/scripts/{scriptUuid}/assignments/{assignmentUuid}PUT1mdm/scripts/{scriptUuid}/updateassignmentsPOST116/mdm/scripts/{scriptUuid}/assignments/{assignmentUuid}DELETE1mdm/scripts/{scriptUuid}/updateassignmentsPOST1 Upon upgrading to the applicable Workspace ONE UEM release, the APIs noted above will be removed and no longer operational. Attempting to access any of these APIs will result in a HTTP 410 response code.Release Update: Above mentioned changes have been released in UEM version 2402
Solution
If any of your applications or processes rely on a deprecated API listed above, you should review the provided list and adopt an alternative, before upgrading to Workspace ONE UEM versions with applicable changes. Check release notes of the upcoming UEM versions to affirm these changes. We will keep this article up to date with additional information in a timely manner. Please subscribe to this article to be notified when updates are available.
