To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112709
User unordained changed the following:
What |Old value |New value
================================================================================
Summary|cross-domain webdav NTLM a|webdav NTLM authentication
|uthentication newly broken| newly (re-)broken
--------------------------------------------------------------------------------
------- Additional comments from unordai...@openoffice.org Tue Sep 21 22:20:56
+0000 2010 -------
New testing:
- On Windows XP, I'm no longer having problems with NTLMv1. But I do get
"general internet error" if OOO 3.2.1 is launched on a Windows 7 or Windows
Server 2008 machine, against that same WebDAV server. MS Word, talking to that
same server, has no issues. I'm using jCIFS's HTTP filter for NTLMv1. The bad
behavior looks like this: request/response, prompt, request/response, request/
response (start over?), prompt, request/response, general internet error.
Server-side, I don't see any failures, other than OOO just not following-
through with a third request/response to finish the challenge. Good behavior
(from Windows XP clients) looks like: request/response, prompt, request/
response, request/response - PROPFIND, HEAD, GET, PROPFIND.
- I've tried switching to NTLMv2 on the WebDAV server, in the hopes that this
is caused by Windows' minimum security level (lmcompatibilitylevel) though I
haven't been able to either replicate the problem in XP, nor make it disappear
in 2k8, by increasing/decreasing this setting from its defaults. I use Jespa
(IOPlex) for NTLMv2, and I found that Jespa had an update as of "1.1.0b2 July
23, 2010" that might have fixed the "not a type 1 message" errors I was seeing
previously when accessing jespa 1.0.4 from OOO 3.2.1, which originally caused
me to stick with NTLMv1. So I updated to jespa 1.1.2, but I still get "not a
type 1 message" when using OOO 3.2.1, regardless of the version of Windows I
try from. It errors out at
java.io.IOException: Not a Type 1 message.
at jcifs.ntlmssp.Type1Message.parse(Type1Message.java:232)
at jcifs.ntlmssp.Type1Message.<init>(Type1Message.java:88)
at jespa.ntlm.NtlmSecurityProvider.acceptSecContext
(NtlmSecurityProvider.java:1045)
Again, MS Word has no problem accessing that same WebDAV server, with either
NTLM v1 or v2. I don't see any difference in behavior in OOO when either
explictly entering username/password, or using [x] system credentials.
I'm going to try OOO 3.3 beta when I get a chance, and we'll also try slightly
older (3.2.0-ish) versions to see if this is a regression.
All of this new testing was done from inside the network, from other machines
in the same Domain (not cross-domain). My original report was related, but I
hadn't really pinned the problem down.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org
For additional commands, e-mail: issues-h...@ucb.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
