[Bug]: OAuth SMTP Authentication Settings Reset After Upgrade to 10.3.1

[dpuffenberger]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

While performing verification checks after upgrading my DNN installations to 10.3.1, I discovered that the sites using OAuth for SMTP Authentication were no longer authorized and unable to send transactional email messages.

Additionally, each one was missing the client secret for the "Auth Provider" that was valid prior to the upgrade.

At first I thought it was a fluke, because I've never encountered this with previous upgrades, but it has been a very consistent problem when upgrading to this version.

Fortunately, reauthenticating the token with the provider works, so I am able to restore email service for these installations, but it was not something I was expecting to do.

Steps to reproduce?

1. Setup OAuth SMTP Authentication on DNN 9 or later
2. Upgrade the installation as documented to version of DNN 10.3.1
3. Attempt to send a Transactional Email or check the SMTP Server Settings

Current Behavior

Installation is unable to send transactional emails after upgrade. The client secret is missing from the SMTP Server configuration settings and the "configuration completed" message is no longer displayed.

Expected Behavior

Installation is able to send transactional emails after upgrade. The client secret remains shown as a populated password on the SMTP Server configuration settings page and the "configuration completed" message is displayed.

Relevant log output

Anything else?

No response

Affected Versions

10.3.1 (latest release)

What browsers are you seeing the problem on?

Microsoft Edge, Safari, Chrome, Firefox

Code of Conduct

• I agree to follow this project's Code of Conduct

[bdukes]

Can you provide more details about which versions you were upgrading from? Also, do you happen to be running this in a FIPS-compliant environment?

[dpuffenberger]

Sure. I was primarily upgrading installations running version 9.13.8. However, one was running version 10.2.1.

I followed the steps to upgrade all of them to version 10.2.4 before the making the jump to 10.3.1.

All the installations are using Upendo's FIPS AES Crypto Provider for cryptography to utilize AES internally but none of them are under any requirements to be FIPS-compliant.

That said, I have pushed upgrades to earlier versions of 10 on installations utilizing this same cryptography provider without any issues. Some were 9.x to 10.x and others were 10.x to 10.x.

So, I was a bit surprised to encounter it with this release.

Hope this helps.