at SmarterTrack.HelperClasses.Security.OAuth2.<InitialAuthenticate>d__5.MoveNext()
    StatusCode: 401 

    ResponseBody: {"error":"invalid_client","error_description":"AADSTS7000222: The provided client secret keys for app '52b21753-****-****-****-d88f0ed06f73' are expired. 

I believe in ST you guys are using secret key which has expired.

Hello Babar, I'm sorry to hear you're having trouble with this. I believe the OAuth components were updated in a later build and I recommend moving to the latest public release to see if these issues are resolved there. If the upgrade doesn't help though please submit a support ticket and we'd be happy to take a look for you!

Hello Kyle, I am having the same issue. It seems client secret for you app in Azure are expired and it will affect many users. My build is 8572.

Hi Fabio, thanks for your follow up on this. The client secret has already been updated and you can find that in our latest public release build. That should get you going in the right direction :-)

Well we should be allowed to use our own azure app secret key. Instead of dependency for build update. 

Well we should be allowed to use our own azure app secret key. Instead of dependency for build update. 

Kyle, does this mean that those who do not have the latest version and active support for SmarterTrack will no longer be able to use oAuth for MS365? This does not seem correct to me, since those who purchased the software and do not want to renew will no longer be able to use this function. We should be allowed to use our own azure app secret key, instead of dependency for build update and consequent renewal of support $$$.

Hello,

Thank you for reaching out again. The client secret required for Office365 integration involves a specific approval process with Microsoft, which is why we manage and update it in our latest builds. This ensures that the OAuth process continues to work smoothly for all users. Unfortunately, using a custom client secret for this purpose is impossible due to these restrictions. We are, however, looking into better methods that do not require upgrading for future builds. 

Please feel free to reach out if you need any further assistance.

Kind regards,

We don’t want to buy upgrade however we want to connect our MS365 mailbox in ST please provide us a patch without any cost. Thx

If you truly believe you should't need to pay for updates for all the work we do to continually keep our product working with all the changes occurring on the Internet, you should probably find another provider. It's not just an API key, Microsoft and Google are sunsetting a ton of stuff and were constantly trying to accommodate.  

Dear Tim, I understand your concerns but this is mot fair with customers to generate secret key in azure with 1 or 2 year expiry. You have an option there to generate key for 5 years. 

If I am allow to ask can you please tell us all what expiry date of secret key in your new installer?

This is a valid concern, please consider generating a secret key for maximum duration to facilitate customers who own a perpectual license key.

It's like you didn't even read my post. Let me try again... It's not just the API key.  Since 2022 (which I believe one of you is running a build from then), things have changed.  Microsoft has changed their API's and how things work and we have had to accommodate when those happen, it is a never ending process.  In addition, we add new features and we do security updates etc.  This is why companies who develop software now offer what we call maintenance and support.  What you bought SmarterMail you got a year of maintaince and support and we provided you continual updates.  After that year, you must pay for maintenance and support if you would like more updates. 

Dear Tim,

I wanted to inquire about the expiration date of the secret key. It seems that with the ST perpetual key, from your side there is an enforcement that blocks customers from continuing to use SmarterTrack with their MS365 accounts.

I am sure it would be in your knowledge that there’s an option in the Azure portal to generate the secret key with a custom period. You could have generated key for longer durations.

If there were any issues other than the expiration of the APP secret key, they would be understandable. Because the current build we are running almost an year old which was working fine days ago and suddenly stop working due to ST app key expiration.
However, in this case, I would like to make a humble request: if you plan to generate a new secret key, could you please use the custom period option in Azure to extend its validity for a longer period?

I can confirm that with the latest ST installer, there is no error.

As per Microsoft's documentation, while you can specify the expiration for a client secret, they limit the lifetime for the secret to 24 months. Microsoft used to offer the ability to get secrets that had a lifetime of up to 99 years, but that changed in April 2021. As we adapted to shifts in Microsoft's security requirements and APIs, we needed to create new client secrets with the necessary permissions.

Below are a couple references to the information available from Microsoft.