Platform Update
Starting in March 2026, the global Certificate Authority (CA) and browser community (CA/Browser Forum) reduced the maximum lifetime of publicly trusted TLS certificates from 398 days to 200 days. This is the first step in a multi-year transition toward even shorter 47-day lifecycles by 2029. Please see this article for details.
What to look out for
- If you generate your own certificates, please ensure your technical teams are aware of the 200-day limit that went into effect on March 15, 2026. Manual renewals are now higher risk; a missed renewal will result in "Insecure Connection" browser warnings for your end-users.
- If we generate certificates for you today, that will remain unchanged, and our interactions will look the same as they do already. We will simply own the increased cadence of certificate expiration and provisioning.
The timeline
- On March 15, 2026, the maximum lifetime for a TLS certificate was reduced from 398 days to 200 days.
- As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.
- As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.
Why is this happening?
Shorter lifecycles enhance security by:
- Reducing Risk: If a security key is ever compromised, it is valid for a much shorter period.
- Increasing Agility: It forces the industry to adopt automated renewal processes, ensuring that our infrastructure can quickly adapt to new security threats or encryption standards.
We are here to support you through this transition. If you have questions about how these changes impact your specific setup, please reach out to our support team: https://www.tylertech.com/client-support/data-insights-support.
Deprecations & Removals
Getty Images Library
The Getty Images library will be removed and will be unavailable for new images starting July 15, 2026. For the latest timeline updates, please refer to our Deprecation Roadmap.
What this means:
- Existing Getty images will remain in place within current Stories and will not be removed or altered as part of this change.
- Users will be able to continue editing existing Getty images within their Stories, including cropping or replacing them with their own uploaded images.
- Starting July 15, 2026, users will need to upload their own images when adding new images to new or existing Stories.
If you have questions, please contact your Client Success Manager.
Bug Fixes
- Resolved an issue preventing users from seeing the full description for “Featured Content Using this Data” on the About page of a dataset. Long descriptions, which were previously cut off, now end with an ellipsis. This lets users know there is more information that can be viewed when navigating to the asset.
- Resolved an issue when viewing mobile sites on Firefox. Previously, sites would display with unnecessary white space on the sides. Sites now display at the proper width.
- Resolved an issue related to the Last Updated date for assets on the Assets Page. Previously, the date reflected the most recent data update. The Last Updated date now displays the most recent date, accounting for both data updates and metadata updates.
- Fixed an issue related to shapefile export coordinate systems. Previously, these exports used the non-standard "WGS84(DD)", which caused some GIS software to fail to recognize the coordinate reference system. This prevented coordinate transformations from being applied. Shapefile exports now use the standard "WGS 84”, allowing affected software to correctly recognize and apply coordinate transformations.
Comments
Article is closed for comments.