Hello Samuel and Brian,

Reason customer was looking at the Kerberos route is they found the following error on 1-2 workstation's in their Environment:

Microsoft-Windows-Security-Kerbero
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server (Customer's LF SQL Service Account Name). The target name used was (Name of Customer LF Server). This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (CUSTOMERSNAME.LOCAL) is different from the client domain (CUSTOMERSNAME.LOCAL), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

The thing is, the do not have:

1. Any SPN's configured

2. Kerberos Key Distribution Center configured

Any pointers greatly appreciated,

Jeff Curtis

Hi Jeff,

Whether the customer realizes it or not, they have tons of SPNs configured (just not manually) as well as KDC, as those are foundational components of an Active Directory domain. Domain Controllers serve as Kerberos KDCs. Laserfiche applications automatically set SPNs during installation.

I would first check what identity your Laserfiche Server instance is running under. I suspect it may be running as the "LF SQL Service Account", because Laserfiche client applications should, to my knowledge, never directly connect to SQL.

Cheers,