pabely ✭✭✭✭✭

I'm not sure that would help you, even if you had a bulletproof MS-SQL to PostgreSQL conversion Tool. I know of a customer running with the MySQL Database type who still has these exact issues.

Are all your States linked to SLAs? Do you have specific Actions in your SLA Rules?

Which Database type do you use?

[deleted]

Yes, just use the readme from HF1 to deploy the perl fixes. Doing it manually is actually the only method.

I feel your pain but things do seem a lot better across our customer base it seems since HF2 + HF3 was introduced.

FYI, this is what has come back from support via my case - * If you're already on HF2 or HF3, and haven’t applied the Perl update (originally in HF1), then yes—those manual steps still need to be completed to fully address CVE-2023-7101.

I have logged a case with support already because it is confusing. I took version 0.66 being the good version so we are Ok for CVE-2023-7071 but the way I read it, if anything has access to that folder then you have much wider security issues to worry about!

That is disappointing for you, still 400 BAD_REQUEST invalid grant seen? What is the EntraID error code shown in the square brackets?

Yes I have worked with her before, she will keep a case open until you are happy rather than wanting to close due to inactivity for a couple of days as some do.

I think it is a little more than that as it has multiple .jar files whereas the original temp fix was just a single .jar file, it has a revised build number as well, 860 vs 827.

Are you using G-Mail or MS365 Mailboxes? 

We have had another 3 customers upgrade over last weekend and feedback so far is good (all MS EntraID Office365 Mailboxes - not G-Mail OAUTH).

Hi @"Psihawk" Good, do share any useful feedback which you get from them.

Hey! We're all here, it make life easier for each other. Hopefully, you have a tidy solution now.

Are you not using Google Mail and it's own implementation of OAUTH2 and thus this might be a very different issue for you?

HF3 replaces the temporary fix where you had to append the whd-peristance.jar if using a MS-SQL Database type. I would create a new secret in the EntraID Register App and then use this new Secret Value in WHD Incoming Mailbox Setup screen and see if issue then goes away.

Do you have a case open with SW Support, the EntraID error 9002313 seems similar to this learn.microsoft.com/.../how-to-fix-azure-ad-api-error-invalid-grant-aadsts which references https://stackoverflow.com/questions/56799177/invalid-grant-error-when-obtaining-access-token Might be worth asking them if they are passing the…

Did you apply the HF3 as well, create a new secret, and re-authorize?

Feedback we have from other sites is HF2 build with HF3 on top is good.

Usually controlled via /etc/init.d calling the /usr/local/webhelpdesk/whd.sh start script. There are other ways of doing it in CentOS like crontab see https://unix.stackexchange.com/questions/148754/how-to-start-application-after-login-on-centos

@"hogancvsd" I have just gone back through my records and we had a customer who also uses Google Mail and had exactly the same issue when they moved to the 12.8.5 release. In the end, we found they had failed to run the migrate.bat as @"jplurker" describes. Once that was done the issue became resolved.

Google OAUTH - this whole thread is to do with issues using MS & EntraID, might require a new thread......

I would consider Inbound Mail not working a P1 scenario. What has Support said? What release version are you running?

Incorrect, it is written to the database encrypted. 

I would think a 500 Internal Server Error is a problem with the Exchange Online Node you are connecting to or connectivity to it temporarily. 

Have you re-authorised ?

That will be because you are running on Windows Server 2022 or Windows 11? See stackoverflow.com/.../trouble-with-windows-11-dll-during-launching-a-installer

Be aware there is a 12.8.5 HF3 now which replaces the emergency fix on HF2 for those running MS-SQL type databases

The KB article supplied by @"donrobert5" is good but if it does not answer your question then please supply the OS type the WHD is installed upon, it will help isolate any variation that might be present.