SDP users are assigned an internal Cato ID as part of the Cato Management Application and Cato’s APIs. To support upcoming features and enhancements, Cato is creating new internal IDs for SDP users.
Starting on June 4, 2023, we are assigning a new internal ID to each SDP user. It’s possible that these new IDs will have an impact on API scripts and queries for SDP users that are hard-coded for the previous IDs.
We recommend that you review the API scripts and make sure that they aren’t hard-coded to use the existing internal ID for SDP users.
What Changes Do We Need to Make?
Review the scripts and settings for Cato’s API queries and make sure that they are not using the internal ID for SDP users.
Customers that created long term SDP user analytics with the entityLookup and/or accountSnapshot APIs might use the SDP user IDs. Customers that use the eventsFeed API are not impacted.
What Is the Impact to My Account?
After June 4, 2023, dashboards or historical analytics that are hard-coded for the previous internal IDs for SDP users may experience issues or might not behave as expected.
These are the API types that are changing:
- AccountMetrics (id)
- AccountSnapshot (id)
- AppStatsFieldName (src_site_id & dest_site_id)
- Type = vpnUser
- EventFieldName (src_site_id & src_or_dest_site_id)
Who Do I Talk to If I Have Questions?
Please contact Support.
Please sign in to leave a comment.