Darryl Young wrote: > In our VDrive that integrates XXE with our XDocs CMS, we use the > following code to call up your AuthenticationDialog: > > PasswordAuthentication pwAuth = Authenticator.requestPasswordAuthentication( > host, null, port, "http", realm, scheme); > > The issue we are having is as follows: > -- If the user makes an error in the initial login, then subsequent > calls to the "requestPasswordAuthentication" method > does not bring up the Authentication dialog, but rather the > previous/cached PasswordAuthentication value is returned > containing the first incorrect login credentials. (This happens whether > we check the "Remember Username and Password" checkbox, or not). > > Therefore, the only way we are currently able to get logged in after > such a series of events is to shut down XXE and start over. > > *Question: *Is there a call that I can access, that would allow me to > reset the cached PasswordAuthentication value when I detect > a login failure such as described above? >
No. > If not, do you have a recommendation as to how I might resolve this issue? > This is clearly a bug. Sorry for that. We'll fix this bug in next release[*] (~February 2010). Meanwhile, I don't see any workaround other than coding and installing your own java.net.Authenticator. --- [*] It's not possible to detect a login failure on XXE's side. (If you know how to do that, you are welcome to inform us.) The fix will probably be based on heuristics. We'll also add a public, documented, API (and may be also a UI) which allows to clear the password cache.
