Santy, Michael wrote: > > I'm using XXE to edit documents stored on a remote server that is > protected with NTLM authentication. The authentication itself works > just fine, but the credentials are not being properly cached between > editing sessions. I have tracked this down to a slight problem in the > AuthenticatorModuleImpl class. > > When a java.net.Authenticator is challanged for credentials in NTLM > scheme, a call to java.net.Authenticator's getRequestingPrompt() will > return an empty string (not a null as I would expect). When this is > flushed out to the preferences.properties and read back in, the prompt > is read back in as a null value. This causes the > AuthenticatorModuleImpl.Entry method boolean equals to fail on otherwise > equal entries which means that the AuthenticatorModuleImpl doesn't > recognize your saved credentials. In order to fix this issue, you can > modify the AuthenticatorModuleImpl.Entry.parse method from: > > if (line.length() > 7) > entry.prompt = line.substring(7); > > to: > > if (line.length() > 7) > entry.prompt = line.substring(7); > else > entry.prompt = ""; > > Please let me know if I'm not being clear enough.
No. It's crystal clear. We've already modified AuthenticatorModuleImpl to fix this problem. We did something slightly more complicated to make a difference between a null prompt and an empty prompt. (AuthenticatorModuleImpl.java sent in a private email.) > Any word on a release date for XXE > 3.7.0? XXE v3.7.1. Before the end of this month. I'll point you to the beta in a few days.
