I looked at NTLMEngine interface, that's not going to help because I don't have password , I have hashed password and that's the basic reason why I can't use ntcredential, etc provided by httpclient.
Thanks Nitin > On May 31, 2014, at 9:36 AM, Nitin Handa <[email protected]> wrote: > > Can you please explain how will implementing NTLMEngine help in my use case? > > Thanks, > Nitin > >>> On May 31, 2014, at 8:34 AM, Oleg Kalnichevski <[email protected]> wrote: >>> >>> On Fri, 2014-05-30 at 15:57 -0700, Nitin Handa wrote: >>> I want do NTLM authentication and also want to cache connection for >>> future requests by same user. Since NTLM is connection based so we cant >>> use same connection for different users. >>> >>> I looked at this link which exactly describes my requirement: >>> http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html#d5e715 >>> >>> Only caveat is that I don't want to use httpclient for NTLM >>> authentication because i want to manually create Type1 and Type3 >>> messages and stick into http headers. But i want to use connection >>> persistence feature described in above link to make sure that connection >>> is not used by any other user. >>> >>> So I am thinking that I can cache HttpClientContext object per session >>> id (represents a user) and then use to for outbound calls. Do you think >>> is viable and appropriate solution? if not then please provide >>> recommendations. >> >> If all you want is to manually generate Type1 and Type3 NTLM messages >> why would not you just implement a custom NTLMEngine or AuthScheme? >> >> Oleg >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
