We do testing of our SimpleRisk releases across several different platforms, but there's no way for us to replicate every unique customer environment to make sure that the SimpleRisk instructions will work the same way every time. Thus, in order to assist our customers in checking their instances for any issues, we've added a "Health Check" to the SimpleRisk application. This Health Check will check your SimpleRisk instance for various common issues such as having an application and database version mismatch, connectivity issues between your system and ours, missing extensions, MySQL STRICT mode enabled, and file permission issues. See the example Health Check below:
By examining this Health Check, we can clearly see the red "X" indicating that the PHP "ldap" extension is not loaded. This isn't a big deal as it's only required for doing Active Directory authentication using the Custom Authentication Extra, but it does give us a clear indicator that our configuration is not optimal. In this case, searching the SimpleRisk Solutions page for "ldap" would find us two different pages that both provide instruction on how to properly get LDAP working for SimpleRisk. To view the SimpleRisk Health Check, select the "Configure" menu at the top, followed by the "Health Check" menu at the left.
The Health Check does a good job of showing issues with various SimpleRisk components, but it doesn't help much with another very common setup issue. That is when SimpleRisk cannot communicate with the API. To test this, go to servername/api/whoami while logged in to SimpleRisk and you should see a JSON response with the username you are logged in as. If this doesn't work, then you should probably take a look at the "How do I enable the SimpleRisk API" documentation.