SendGrid authentication changes - effective April 17th 2019

Modified on: Mon, 4 Jan, 2021 at 5:44 PM

If you have two-factor authentication (2FA) enabled for your SendGrid account, you need to temporarily disable 2FA before April 17, 2019. Not making these changes will disrupt all your customer notifications from Chargebee.


What is the change?


Starting April 17th, 2019, SendGrid will no longer accept basic authentication (username and password) for calls to SendGrid's v2 API, v3 API, or SMTP for those who have 2FA enabled. Calls using basic authentication for users with 2FA will be rejected.


Whom does it impact and how?


All SendGrid users who have 2FA enabled AND use basic authentication will be impacted by this change. If you have configured your own SendGrid account in Chargebee, this authentication change will restrict all subscription emails, such as invoices, renewal reminders, dunning emails, etc., going out from Chargebee.


From April 17, 2019, SendGrid users who have 2FA enabled (via SMS or through the Authy App) will not be able to use basic authentication (username and password) over the Sendgrid v2API, v3API, or SMTP. 


How is Chargebee handling this?


Since SendGrid had only communicated this to their customers who had enabled 2FA, we were made aware of this change only on April 12th, 2019 by one of our customers. Our SMTP Configuration settings in Chargebee will now allow you to enter your SendGrid API address, thereby adhering to SendGrid’s authentication requirements


Next steps


Navigate to Settings > Configure Chargebee > Email notifications > Change SMTP settings

After entering your SMTP Server address, enter API Key in the User name field and your actual API key in the password field. Refer to the image below:


Related articles and Documentation

API Key Authentication

Configuring SMTP in Chargebee



A
Anthony is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
×