FortiSIEM with certificate from Microsoft AD CS

[mngveliki]

Hello,

Since I did the integration of an ssl certificate signed by a Microsoft adcs certificate authority. I have ssl errors in the phoenix.log related to the phMonitorSupervisor. And in the Cloud Health section, the supervisor status is critical.



On the other hand, I have a valid certificate when I connect in the WEBUI of FortiSIEM.

In the FortiSiem documentation, it describes the procedure to add a signed certificate. But I have an impression that it is only for ca authorities like Entrust, etc.

So, should we add the root CA of ADCS in the OS certificates (rocky Linux)?

[ReisMacand]

It's possible that the SSL errors in the Phoenix log and the critical status of the supervisor in the Cloud Health section could be related to the SSL certificate integration. In order to diagnose and resolve the issue, it may be necessary to troubleshoot further.

[FrankytheMobster]

I'm sorry to hear that you're running into SSL errors with your FortiSIEM integration. From my understanding, adding the root CA of ADCS in the OS certificates could solve this issue. I would recommend trying that to see if it resolves the SSL errors you're experiencing.

Additionally, ensure that you follow the FortiSiem documentation to add a signed certificate, even for CA authorities like Entrust. It's always best to follow the documentation provided. You may also find it helpful to know about other ways of microsoft certifications. Good luck with your troubleshooting.

[clarta]

I was exploring different tools to streamline software setup in our office environment, and I noticed that kms auto has a simple interface that makes it easy to navigate. It’s interesting to see how different dashboards and menus are structured, and testing the features helps understand how such tools organize tasks efficiently.