Password with special character and using Forms authentication makes the GFI MailArchiver Import Export Tool fail to connect

Versions / Builds Affected

until 20130723

Status

Resolved

Problem Summary

Password with special character and using Forms authentication makes IET fail to connect

TT / JIRAID

1699

How to Identify

1. Server is configured to for Forms authentication 2. User has a special character like & in their password 3. The IET fails to connect to the server 4. The username and password were entered correctly entered into the IET's dialog 5. The user account is NOT locked or disabled in AD 6. When using IE the very same user can log into the web interface properly The W3C logs from the IIS server show a 420 error and the special character in the password is not escaped: 2013-10-06 11:19:30 ::1 POST /MailArchiver/services/search.asmx - 80 - ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.269) 420 0 0 9 2013-10-06 11:19:33 ::1 POST /MailArchiver/securitytest.ashx username=johndoe&password=Password&1 80 - ::1 - 420 0 0 3133 In the example above the password was set to: Password&1 ..\MarcImportExport\DebugLogs\BET_Connection.log 2013-10-06,12:20:48,060,1,"#000016BC","#00000001","error ","BET_Connection","error: Connection failed - MArcImportExport.ImportToolsException: Enter User credentials ---> System.Net.WebException: The remote server returned an error: (420). ; at System.Net.HttpWebRequest.GetResponse() ; at MArcImportExport.BulkExport.BulkExport.FormsAuthentication() ; --- End of inner exception stack trace --- ; at MArcImportExport.BulkExport.BulkExport.FormsAuthentication() ; at MArcImportExport.BulkExport.BulkExport.get_SearchService() ; at MArcImportExport.BulkExport.BulkExport.VerifyConnectionToSearch() ; at MArcImportExport.BulkExport.ConnectForm.Event_bwConnectionCheck_DoWork(Object sender, DoWorkEventArgs e) ; at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) ; at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)"

Workaround / Fix Details

Use Windows Authentication. Or Change the password so that it does not contain special characters. ---- Fixed in MARC 2013 R2

Required Actions

Upgrade to MARC 2013 R2 or newer or use workaround.