Browser based login via NTLMv2

--94eb2c0c5e669a63770541f5ba03
Content-Type: text/plain; charset=UTF-8

Hello folks,

I'm trying to get Jasig CAS to play nicely with JCIFS and NTLMv2 and seem
to be missing part of the puzzle.

I see the HTTP servlet for NTLM doesn't work in JCIFS with v2 but I don't
think that issue affects me directly.

CAS passes off an NTLMv2 Type 3 ticket to JCIFS and from that Smb.login()
is called. The ticket has no password just the hashes. But then it lands at

public static byte[] nTOWFv2(String domain, String username, String
password)

when processing the Smb login which then tries to process the password
which of course it doesn't have.

I see claims that NTLMv2 works, but is it the case that it works, but not
for browsers? Or have I missed something?

Thanks

Tom

--94eb2c0c5e669a63770541f5ba03
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello folks,<div><br></div><div>I&#39;m trying to get Jasi=
g CAS to play nicely with JCIFS and NTLMv2 and seem to be missing part of t=
he puzzle.</div><div><br></div><div>I see the HTTP servlet for NTLM doesn&#=
39;t work in JCIFS with v2 but I don&#39;t think that issue affects me dire=
ctly.</div><div><br></div><div>CAS passes off an NTLMv2 Type 3 ticket to JC=
IFS and from that Smb.login() is called. The ticket has no password just th=
e hashes. But then it lands at=C2=A0</div><div><br></div><div>public static=
 byte[] nTOWFv2(String domain, String username, String password)</div><div>=
<br></div><div>when processing the Smb login which then tries to process th=
e password which of course it doesn&#39;t have.</div><div><br></div><div>I =
see claims that NTLMv2 works, but is it the case that it works, but not for=
 browsers? Or have I missed something?</div><div><br></div><div>Thanks</div=
><div><br></div><div>Tom
</div></div>

--94eb2c0c5e669a63770541f5ba03--