Notifications don’t work when Windows Authentication (AD Integration) is used
In some scenarios the notification function will stop functioning after AD Integrated authentication is turned on.This could happen if the service account used for CS can't login to the application with single sign on.
When sending notifications you might see Access denied in hisend logfiles
Open the last modified hisend.<Scannumber>.log the following folder. (depending on your installation)
C:\Program Files (x86)\Hisoftware\Compliance Sheriff\logs
C:\Program Files (x86)\Cryptzone\Compliance Sheriff\logs
Search for entries that looks like bellow.
03/10/2016 11:42:53 Requesting http://mycomplianceurl.com/ComplianceSheriff_<CustomerName>/
03/10/2016 11:42:54 Access is denied.
When the worker agent that is responsible for creating notifications are to create the reports. It does a HTTP request to the web application.
This request needs to be authenticated, to be able to do this Internet Explorer needs to be configured to automatically send current user name and password.Resolution:
To resolve this issue automatic login in IE needs to be enabled.In a distributed installation this needs to be done on all servers that is running Worker agent role and the web server role.
Make sure the Service account that is used for Compliance Sheriff is a member of the Compliance Sheriff Administrators group in your Active Directory.
Start Internet Explorer as the service account used for Compliance Sheriff.
You can either log directly into the server as the service account or use the “RunAs” feature.
Open Tools-> Internet Options.
Click on the Security Tab.
Click on Trusted Sites.
Click on Sites and add the URL that is used to browse to Compliance Sheriff.
Click on Close to save and close the Trusted Sites dialog box.
Click on Functional Level.
Scroll to the bottom and Select Automatic login with current user and password.
Click on OK to save and close the Security Settings dialog box.
Click on OK to Close the Internet Options dialog box.
Now Try to send a new notification and see if it works.Affected Versions:Compliance Sheriff 4.2.x
Compliance Sheriff 4.3.x