Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Authenticator and re-authentication

 
Sander Smith
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Rancher
Posts: 42967
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic