[jcifs] 1.3.x filter authentication problem

[Caldarale, Charles R]

> From:
> jcifs-bounces+chuck.caldarale=unisys.com at lists.samba.org
> [mailto:jcifs-bounces+chuck.caldarale=unisys.com at lists.samba.o
> rg] On Behalf Of John.Baker at barclayscapital.com
> Subject: RE: [jcifs] 1.3.x filter authentication problem
>
> How does one create two instances of Jcifs, with different
> configurations, within one VM?
>
>
> John
>
> > -----Original Message-----
> > From:
> > jcifs-bounces+john.baker=barclayscapital.com at lists.samba.org
> > [mailto:jcifs-bounces+john.baker=barclayscapital.com at lists.sam
> > ba.org] On Behalf Of Michael B Allen
> > Sent: 09 February 2009 16:25
> > To: raintrain at gmx.at
> > Cc: jcifs at lists.samba.org
> > Subject: Re: [jcifs] 1.3.x filter authentication problem
> >
> > On Mon, Feb 9, 2009 at 4:45 AM,  <raintrain at gmx.at> wrote:
> > > I have a web application with http filter authentication
> > and standard user/pwd login.
> > >
> > > If the user was logged in through the http filter and logs
> > out, it's possible to log in with username and password combination.
> > >
> > > For the http filter i have to use the following options:
> > >
> > > jcifs.smb.client.useExtendedSecurity=false and
> > > jcifs.smb.lmCompatibility=0
> > >
> > >
> > > The problem is, that the user can't login with
> > username/password after the http filter sets the properties!
> >
> > This is an issue between init-params being dynamic and yet
> > the jcifs.Config properties are static. So technically you
> > cannot reliably set those properties from within init-params.
> > You must use a -Djcifs.properties=jcifs.prp file and load the
> > JCIFS properties from the command line of your servlet container.
> >
> > > I can't use 1.3.x to log in with http filter and without!
> >
> > Or use 1.2. The reason this issue suddenly occurs in 1.3 is
> > because the two above mentioned property defaults have
> > changed and as mentioned above, cannot be set using
> > init-params. There's nothing different about the 1.2 filter.
> > The JCIFS NTLM HTTP Filter has not been modified at all in
> > several years.
> >
> > Note that the FAQ and NTLM HTTP Authentication Filter
> > documentation has recently been updated with important
> > information regarding the Filter and NTLMv2. In short, the
> > Filter doesn't work anymore and is being removed.
> >
> > Mike
> >
> > --
> > Michael B Allen
> > Java Active Directory Integration
> > http://www.ioplex.com/
> >
> _______________________________________________
>
> This e-mail may contain information that is confidential,
> privileged or otherwise protected from disclosure. If you are
> not an intended recipient of this e-mail, do not duplicate or
> redistribute it by any means. Please delete it and any
> attachments and notify the sender that you have received it
> in error. Unless specifically indicated, this e-mail is not
> an offer to buy or sell or a solicitation to buy or sell any
> securities, investment products or other financial product or
> service, an official confirmation of any transaction, or an
> official statement of Barclays. Any views or opinions
> presented are solely those of the author and do not
> necessarily represent those of Barclays. This e-mail is
> subject to terms available at the following link:
> www.barcap.com/emaildisclaimer. By messaging with Barclays
> you consent to the foregoing.  Barclays Capital is the
> investment banking division of Barclays Bank PLC, a company
> registered in England (number 1026167) with its registered
> office at 1 Churchill Place, London, E14 5HP.  This email may
> relate to or be sent from other members of the Barclays Group.
> _______________________________________________
>