Francois PIETTE wrote:
>>> Should ICS be responsible for domain/user parsing out of a single
>>> property
>>> or should a new property with domain added ?
>> I think not, unless the component itself test for the combination that
>> works.
> That's not logical. The NTLM message has two different parts for domain
> name and user name. Putting the right name in the right part would solve
> all problem imo. 

I second that.

> It is possible that some smart proxies take care of
> extracting domain name from username if domain part is empty in the
> message.
> And for those smart proxies, you have to provide the right
> separator.

I think they arn't so smart, but just calling LogOnUser() note
that [EMAIL PROTECTED] valid, not only for FTP-proxies. 

>From MSDN: 

[in] A pointer to a null-terminated string that specifies the name of the user. 
This is the name of the user account to log on to. If you use the user 
principal name (UPN) format, [EMAIL PROTECTED], the lpszDomain parameter must 
be NULL. 
[in] A pointer to a null-terminated string that specifies the name of the 
domain or server whose account database contains the lpszUsername account. If 
this parameter is NULL, the user name must be specified in UPN format. If this 
parameter is ".", the function validates the account by using only the local 
account database."

Arno garrels

> If a new domain property is added, nothing prevent the component user from
> ignoring it and still provide domain name and user name in the user name
> part as today, and to rely on the smart proxy to handle that situation. It
> is not worse than today and even provide an enhancement.
> --
To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to