This week's book giveaway is in the OCAJP forum.
We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line!
See this thread for details.
The moose likes Java in General and the fly likes Authenticator and re-authentication Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of OCA Java SE 8 Programmer I Study Guide 1Z0-808 this week in the OCAJP forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "Authenticator and re-authentication" Watch "Authenticator and re-authentication" New topic

Authenticator and re-authentication

Sander Smith

Joined: May 20, 2006
Posts: 4
I have an application that's making HTTP requests to websites by means of a HttpURLConnection object. Occasionally, I need to authenticate to a website, so I've subclassed Authenticator to do this, and made my class active by calling Authenticator.setDefault(). My class overrides getPasswordAuthentication and returns the proper information in a PasswordAuthentication object.

Things work until I need to re-authenticate to the same website. This is important, since the password to the website may have changed since the first connection, or there is some reason to login with different authentication credentials. I find that I can't do this since getPasswordAuthentication never gets called again, but rather the same PasswordAuthentication object (with the now incorrect information) is used.

So my question is: How does the system cache the PasswordAuthentication? Is it based on:
the URL you go to?
the realm you connect to?
it is always the same on regardless of where you connect?

Is there something I can do to force the system to re-authenticate?

Sander Smith
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42952
Not a direct answer, but you can use authentication with [Http]UrlConnection in a more direct way, which is outlined here (applets and other Java code are equal in this regard). That should also handle changing credentials, since no caching takes place.
subject: Authenticator and re-authentication