Spectrus DB: Authentication Failure After LDAP / Active Directory Configuration Changes

The issue can occur when changes are made to the organization's LDAP or Active Directory infrastructure, such as:

• LDAP signing being enabled or modified.
• Active Directory authentication policy updates.
• Changes to certificates used for LDAP communication.
• Other LDAP/AD security or configuration changes that affect authentication workflows.

The issue was resolved by updating the application's authentication configuration to match changes in the customer's LDAP/Active Directory environment. 

Steps Performed

Prerequisites: Admin credentials for ESMC (Enterprise Server Manager Console) and access to the SpectrusDB server.

1. Launch ESMC
   • Navigate to <ACD>\SPECTRUSDB.SRV\ and run esmc.exe
2. Connect to the database schema
   • Connect as an admin user to the affected database schema
3. Navigate to Scripted Actions
   • Switch to the "Scripted Actions" panel in ESMC
4. Open Authentication settings
   • Right-click on the PostgreSQL (or Oracle) database node
   • Select "Authentication"
5. Verify current configuration
   • Confirm that "Custom (Using Script)" is selected as the authentication type
   • Note the selected scripted action in the "OnAuthenticate Script Action" drop-down
6. Enable LDAP Signing
   • In the Authentication Options dialog, toggle ON the LDAP Signing option
   • This enables integrity checking on the LDAP connection, satisfying the domain controller's requirement
   • Toggle OFF the Use SSL option

7. Test authentication

• Click "Check Authentication" (bottom-left of the dialog)
• Enter a valid username and password
• Confirm successful authentication

8. Click OK to save the settings

9. Verify with multiple users

• Have at least one additional user log in to confirm the fix works across accounts