- DigiCert product docs
- IoT Trust Manager
- Upcoming product name changes
Upcoming product name changes
DigiCert is excited to announce upcoming changes in IoT Trust Manager to enhance your user experience. As part of these improvements, we will be renaming certain objects within the platform.
Name changes quick look
Previous name | New name |
|---|---|
Device profiles | Device groups |
Enrollment profiles | Certificate management policies |
Enrollment methods | Certificate management methods |
Opmerking
These name changes will not impact API endpoints or certificate services that currently use the previous names. We are committed to ensuring zero interruption for customers using our previous naming conventions.
Device profiles renamed to Device groups
IoT Trust Manager facilitates certificate management from a device perspective through device records. To better align with our evolving features, such as software updates, device agents, and monitoring, we are renaming Device profiles to Device groups.
Device groups will continue to support all existing features of Device profiles and will expand to include new capabilities over time. This change also paves the way for the future introduction of dynamic device groups.
Impact to API users
A new version of our API will be released to support this name change. Existing API endpoints referencing Device profiles and Device IDs will remain unchanged.
Tip
We recommend adopting the new API version to take advantage of upcoming features linked to Device groups.
Enrollment profiles renamed to Certificate management policies
Device enrollment in IoT Trust Manager can occur through various methods. After reviewing the Enrollment profile’s role and configurations, we have decided to rename it to Certificate management policy to better reflect its purpose.
This change shifts the focus from initial enrollment to ongoing certificate management. Consequently, Enrollment methods will also be renamed to Certificate management methods within the Certificate management policy. Examples include SCEP, EST, ACME, and Certificate request APIs.
Impact to API users
A new version of our API and certificate services will be available to support this name change. Existing API endpoints referencing Enrollment profiles and Enrollment methods will remain unchanged.
Tip
We recommend adopting the new API and certificate services version to benefit from future features tied to Certificate management policies.