To enhance the security of our platform and protect our customers, we are introducing an automatic token deactivation public beta feature on October 8th, 2024, for any HubSpot tokens publicly exposed in GitHub repositories. This update is designed to mitigate the risks of token exposure by automatically deactivating the identified tokens and notifying the affected customers and their associated technical contacts.
The new feature will include the following token types listed below, along with examples of the notifications communicating detected token deactivation:
*Note: Users are responsible for manually generating a new SMTP token after it's been automatically deactivated.
To avoid service disruption, developers using affected tokens (API Keys, Personal Access Keys, Private App Tokens, SMTP Tokens) must ensure they are not exposed in public repositories. Developers must generate new tokens and update their integrations if a token is revoked.
There is a particular concern regarding private apps. Developers using private app tokens should be aware that these tokens will also be subject to the same automatic revocation process.
This feature is being introduced to public beta on October 8th, 2024, and will be live and enforced on April 7th, 2025.
To opt into this beta feature, please refer to the Product Updates by clicking on your HubSpot account's profile picture, navigating to In beta, and clicking on Join Beta. For more information, please refer to the documentation.
Questions or comments? Join us in the developer forums.