[jcifs] How to get jCIFS to always prompt for username and pa ssw ord?

[Greg Schroder]

Thanks for your reply Mike

We have tried a few different variations in web.xml.

It seems the problem is with the domain config, because on our one server
specifying a wins
server and the domain authenticates just fine, with the DC it doesn't. On
the other server
neither works.

Any ideas what could be wrong with our domain config? We outsource the
helpdesk department
and they claim nothing has changed since the errors began.

    <filter>
        <filter-name>NtlmHttpFilter</filter-name>
        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
        <init-param>
            <param-name>jcifs.netbios.wins</param-name>
            <param-value>172.?.?.?,172.?.?.?</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.domain</param-name>
            <param-value>domainname</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.username</param-name>
            <param-value>petrus</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.password</param-name>
            <param-value>padda</param-value>
        </init-param>
    </filter>

If we specified a domain controller along with a username and password, it
only works for
the first login, thereafter it pops up with a login window, where no login
works.

    <filter>
        <filter-name>NtlmHttpFilter</filter-name>
        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
        <!--<init-param>
            <param-name>jcifs.http.domainController</param-name>
            <param-value>172.?.?.?</param-value>
        </init-param>-->
        <init-param>
            <param-name>jcifs.smb.client.domain</param-name>
            <param-value>domainname</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.username</param-name>
            <param-value>petrus</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.password</param-name>
            <param-value>padda</param-value>
        </init-param>
    </filter>

When specifying a domain controller, we tried using a non existant account,
and didn're receive
any error with authenticating with the domain controller in order to
authenticate the user
accessing the page. (Hope I'm making sense here).
What is happening here since even though we specified an invalid account for
contacting the
DC, it still pops up and tries to authenticate the user without giving any
other error. I
expected some sort of authentication failure from the DC?

-----Original Message-----
From: Michael B Allen [mailto:mba2000 at ioplex.com]
Sent: Wednesday, November 01, 2006 4:55 AM
To: Greg Schroder
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] How to get jCIFS to always prompt for username and
passw ord?


I wasn't aware there was a problem with this. If you're not using WINS
you should still be able to use the 'Explicit Domain Controller web.xml
Example'. I suspect you have some other params that are messed up. You
could try posting your filter section and see if anyone can point out
the error.

Mike

On Mon, 30 Oct 2006 11:22:52 +0200
Greg Schroder <SchroderG at teldir.co.za> wrote:

> Hi
> 
> We have been experiencing similar problems to another members posting,
where
> ntlm authentication only works for one user at a time. Every other user
then
> gets a login popup after that, where no login succeeds. This started
> occuring on our one server, after not being able to figure out the cause,
we
> moved our page to another server. It worked fine for nearly a month, until
> it started the same problem. They are Windows 2003 servers, and we have
> tried specifying a specific domain, user and password to contract the
domain
> controller with. Previously we used WINS but we are not using it any
longer.
> If anyone has solved this problem please tell me how? We've looked at the
> accounts on the domain controller etc. and cannot see the problem. Our
> support team say nothing has changed on the server or it's account before
> the problems started.
> 
> Any help appreciated.
> 
> Regards,
> Greg Schroder
> 


-- 
Michael B Allen
PHP Active Directory SSO
http://www.ioplex.com/