Thanks Hussein. ----- Original Message ----- From: "Hussein Shafie" <[email protected]> To: "Darryl Young" <darryly at bluestream.com> Cc: "Jim Tivy" <jimt at bluestream.com>; "Nenad Furtula" <nenadf at bluestream.com>; <xmleditor-support at xmlmind.com> Sent: Monday, March 01, 2010 11:16 AM Subject: Re: [XXE] AuthenticationDialog issue
> Darryl Young wrote: >> Do you have any estimate as to a proposed release date for the new >> version >> of XXE (ie: newer than 4.5.1)? >> > > As always, we are late. Release candidate v4.5.2 should be available at > the end of this week. Official release one week later. > > Excerpts of changes.html > --- > * Added a "Clear cached passwords" button to the "Cached data" > preferences sheet. > > Clicking this button is mainly useful as a workaround for the following > problem: when opening a document stored on a server requiring user > authentication (e.g. a WebDAV server), a user who typed an incorrect > username or password is never prompted again for her/his credentials. > > * Another workaround for the above problem, this time transparent for > the user of XXE, is to specify system property > XXE_CONFIRM_CREDENTIALS_DELAY. > > Example: -DXXE_CONFIRM_CREDENTIALS_DELAY=1000, means wait for at least > 1000 milliseconds before considering that the credentials specified by > the user have been accepted by the server. > > When system property XXE_CONFIRM_CREDENTIALS_DELAY has been specified to > an appropriate number of milliseconds, a user who typed an incorrect > username or password is automatically prompted again for her/his > credentials. However, this workaround, based on a heuristic, may be > tricky to configure and may be not usable for some protocols. For > example, it seems to work for HTTP and it gets in the way for FTP. > --- > > The API corresponding to "Clear cached passwords" is: > com.xmlmind.netutil.AuthenticatorList.clearCredentials() > >
