We are migrating some of our features and offerings to an upgraded version. The details of these upcoming migrations and their impact are listed below.
- Deprecation of username and password-based basic authentication for API v2
- Removal of Deprecated Attributes from User Management APIs
- Deprecation of Amazon Web Services Marketplace App
- Strengthening TLS 1.2 Cipher Suites
Deprecation of username and password-based basic authentication for API v2
To provide enhanced data security, we are deprecating username and password-based basic authentication of Freshservice APIs. After May 31st 2023, only Basic auth with API key will be supported.
Post the deprecation date of May 31, 2023, all API requests using username/password through basic authentication will fail. This means all your workflows and customizations using username/password through basic authentication will fail.
Removal of Deprecated Attributes from User Management APIs
To reduce redundancy in APIs after the enhancements to Freshservice’s user management module, we will remove all deprecated attributes from the Agent and Agent Group APIs by May 31st, 2023.
Post the deprecation date of May 31, 2023, any inputs of API requests that use these attributes will not be accepted. Any responses that contain the ‘Agents’ or ‘Agent Groups’ object will no longer contain these deprecated attributes.
If you have used APIs with any of the attributes listed above in any of the following actions, you may be impacted by this deprecation:
To configure your workflows (Web Requests and Trigger webhook actions)
To customize your portal
To interact with Freshservice instance from any of your custom applications
Deprecation of Amazon Web Services Marketplace App
To empower our power users of AWS cloud with more advanced cloud discovery and management solutions, we will be upgrading you to the AWS Cloud discovery application. As a part of this new upgrade, we will deprecate the Amazon Web Services ( Native AWS app) application from our marketplace on 31st May 2023.
Strengthening TLS 1.2 Cipher Suites
We are updating and implementing new security controls to ensure information systems and customer data used as part of our offerings are protected.
We ended support for the older versions of TLS (1.1 and below) and continued support for TLS 1.2 across our suite of products in April 2020. Next, we will be changing our transport layer security controls to allow only TLS 1.2 Strong cipher suites.
If you’ve built custom integrations with Freshservice, please ensure your API Clients are compatible with the TLS 1.2 Strong cipher suites.
More information on how to test your api client compatibility can be found here.
Please reach out to firstname.lastname@example.org for any support or queries.