Webagent Trace logs show username/UID appended with PAR.

Document ID : KB000051451
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

The username entered by this user in the login form (login.fcc) was testuser04 but somehow the agent trace logs were showing testuser04par.

Agent trace entries were showing string 'par' appended to the uid entries as:

[05/15/2009][00:50:06][1560][5472][439b44a6-0618-4a0cf47e-1560-001f0029][AuthenticateUser]
[User 'testuser04par' is not authenticated by Policy Server.]

Solution

Policy server was installed on windows 2003 and the webagent was residing on IIS6. When the login.fcc file was opened on the windows server with WordPad it showed up as below:

<!-- SiteMinder Encoding=ISO-8859-1; -->
@username=%UserId%
@password=%Password%
@target=%target%
@smerrorpage=https://testlab.smlab.com/Exception.html
@smretries=3
 

But when the same file was opened with NotePad or a Vi based editor it showed up as below:

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Courier New;}{\f1\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\f0\fs20\par
@username=%UserId%\par
@password=%Password%\par
@target=%target%\par
@smerrorpage=https://testlab.smlab.com/Exception.html\par
@smretries=3\f1\par
}
 

As we can see with the login.fcc file open with Notepad there are extra '\par' characters on each line alongwith '\f1' and characterset related characters.

The file was edited to remove these extra characters and the 'par' was no longer appended to the uid.
This was caused by using an incorrect file transfer protocol type, binary, instead of ASCII to transfer the login.fcc files on to the webserver.