[jcifs] JCIFS http filter problem with DC on Win 2003

[Michael B Allen]

Win2K3 requires SMB signatures by default so "preauthentication" is
required. Also, prior to 1.2.8 preauthentication was partly broken.
What version are you using 1.2.9? Try the default setup as shown in the
latest NTLM HTTP Authentication documentation on our website.

Mike

On Fri, 21 Apr 2006 12:37:18 +0200
"Inge Solvoll" <inge.tapestry at gmail.com> wrote:

> I'm having stability issues with NtlmHttpFilter. The authentication works
> transparently most times for most users, but for some of them, no
> "NtlmHttpAuth" attribute is set in the session after NtlmHttpFilter has
> performed its work. On these occations, "manual" logins don't work either
> for these users, they get an exception (SmbException: Access is denied) when
> they try to manually type their username and password in the browser popup.
> 
> A user can achieve successful logins one day, and then fail the next day.
> 
> Any ideas? I'll try to get some more details if needed.
> 
> I've tried some of the ideas in the FAQ:
> - Provide username/password for preauthentication
> - change the jcifs.smb.client.ssnLimit to 1.
> 
> My setup:
> JBoss 4 on Windows 2003
> Domain controller on Windows 2003
> IE6 clients
> 
> 
> <filter>
>     <filter-name>NtlmHttpFilter</filter-name>
>     <filter-class>mypackage.common.filters.NtlmHttpFilter</filter-class>
> <!--  Overrides jcifs NtlmHttpFilter -->
> 
>     <init-param>
>         <param-name>jcifs.smb.client.domain</param-name>
>         <param-value>mydomain.com</param-value>
>     </init-param>
>     <init-param>
>         <param-name>jcifs.http.domainController</param-name>
>         <param-value>10.10.10.10</param-value>
>     </init-param>
> </filter>
>