CTX200927
2016-04-28
1970-01-01
Username is not displaying in the XenMobile NetScaler Connector (XNC) logs.

Symptoms or Error

Username is not displaying?? in the?? XenMobile NetScaler Connector (XNC) logs.
The username field in the XNC logs are empty, as displayed in the following screen shot:

User-added image

When looking into the log files on XNC, you could verify that the user field is empty:

 2013/12/12 15:42:52.961 INFO action=allow; group=XDMSQL(allow); user=; did=androidc11687469; dt=TouchDown; cmd=Ping; ua=TouchDown(MSRPC)/7.3.00052/; ip=192.168.178.102; srvr=192.168.178.235; pid=Static + XDMSQL: Permit Mode; url=servlet/traveler/Microsoft-Server-ActiveSync; cid=0; ea=0 2013/12/12 15:44:21.696 INFO action=allow; group=XDMSQL(allow); user=; did=androidc1624379824; dt=TouchDown; cmd=Ping; ua=TouchDown(MSRPC)/8.1.00052/; ip=192.168.178.102; srvr=192.168.178.234; pid=Static + XDMSQL: Permit Mode; url=Microsoft-Server-ActiveSync; cid=0; ea=0 2013/12/12 15:46:58.555 INFO action=allow; group=XDMSQL(allow); user=; did=androidc11687469; dt=TouchDown; cmd=Ping; ua=TouchDown(MSRPC)/7.3.00052/; ip=192.168.178.102; srvr=192.168.178.235; pid=Static + XDMSQL: Permit Mode; url=servlet/traveler/Microsoft-Server-ActiveSync; cid=0; ea=0 2013/12/12 15:49:01.336 INFO action=allow; group=XDMSQL(allow); user=; did=androidc1624379824; dt=TouchDown; cmd=Ping; ua=TouchDown(MSRPC)/8.1.00052/; ip=192.168.178.102; srvr=192.168.178.234; pid=Static + XDMSQL: Permit Mode; url=Microsoft-Server-ActiveSync; cid=0; ea=0

User-added image


Solution

Note: When using certificate based authorization, the user name might not be visible in the User Name field because it is using the certificate instead of the username/password to authorize.

Ensure that the correct string for the “user” field is used in both callout policies (with and without deviceid):
HTTP.REQ.HEADER("authorization").AFTER_STR("Basic ").B64DECODE.BEFORE_STR(":").HTTP_URL_SAFE

Complete the following steps to resolve this issue:

  1. Edit the string.

  2. Add?? a new entry.

  3. Remove the faulty one?? from each callout policy to make it work.

Note: The wizard would do this automatically, but there might be NetScaler versions in the field that do not have the wizards in place.


Problem Cause

This generally occurs because of misspelling?? in the HTTP Callout policies.
The break occurs when there is NO SPACE after the alphabet c in?? Basic - For example, "Basic".
Ensure that you add a space after 'c' in Basic - "Basic " in the callout.


Applicable Products


 

Join the conversation

Citrix Discussions

Open a case

Citrix Support

特别说明


本文来源为Citrix.com所有,翻译后版权归翻译者所有.如需转载请注明出处.

文档版本


.

广告招租


最新留言


.

广告招租


.