FULL PRODUCT VERSION :
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Darwin MacBook-Pro.local 12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64
A DESCRIPTION OF THE PROBLEM :
If you install a web start app on a web site with authentication, one needs a way to store the credentials, otherwise the user will be bothered every time the app starts. So Web Start has a dialog box where you enter your credentials and box you tick to remember them.
By most accounts, the little box doesn't work, but that's not the bug I'm reporting here. Seemingly it works sometimes, I don't know what goes on with it.
So, there are two possible ways to store credentials. One is if the little box works. The other is to configure your web server to store some credentials in cookies.
In both of these cases there is seemingly no known method to clear these credentials / cookies once stored.
I've tried everything I can think of. removing ~/Library/Application Support/Oracle/Java. I've tried clearing the cache in the Java Cache Viewer. I've tried looking in various plists. I don't know where they are and I shouldn't have to know.
Possibly on Windows one can use IE to clear the cookies (but not credentials). Haven't tested it. On Mac, there is no such option. Clearing Safari certainly doesn't work.
What I've found is that with the credentials it is basically impossible to clear them. I've even tried making the web server deny access with unauthorised response, and Web Start still doesn't take the hint. It tries the credentials again automatically the next time whether you like it or not.
So in summary:
1) Java Web Start's tick box for storing credentials has no means to clear those credentials. Clearing all the Web Start Caches doensn't do the job.
2) Java Web Start's cookie store has no means to clear those cookies. Clearing all the Web Start Caches doesn't do the job.
What should happen:
Clearing the web start cache, at a bare minumum with javaws -uninstall should delete all credentials and cookies. There should also be something in the GUI that does it also.
REGRESSION : Additional Information
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Configure a web server to ask for CREDENTIALS before serving up a Web Start App. Enter username and password into the javaws login dialog. Tick the box to remember the credentials. Now there is no way to clear those credentials..
Configure a web server to send COOKIES before serving up a Web Start App. Now there is no way to clear those credentials..
Try clearing web start cache in Java Cache Viewer.
Try clearing web start cache from command line.
Neither have any effect on stored credentials or stored cookies.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Should be some mechanism to clear credentials
Should be some mechanism to clear cookies.
ACTUAL -
Credentials and cookies are stuck forever.
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Darwin MacBook-Pro.local 12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64
A DESCRIPTION OF THE PROBLEM :
If you install a web start app on a web site with authentication, one needs a way to store the credentials, otherwise the user will be bothered every time the app starts. So Web Start has a dialog box where you enter your credentials and box you tick to remember them.
By most accounts, the little box doesn't work, but that's not the bug I'm reporting here. Seemingly it works sometimes, I don't know what goes on with it.
So, there are two possible ways to store credentials. One is if the little box works. The other is to configure your web server to store some credentials in cookies.
In both of these cases there is seemingly no known method to clear these credentials / cookies once stored.
I've tried everything I can think of. removing ~/Library/Application Support/Oracle/Java. I've tried clearing the cache in the Java Cache Viewer. I've tried looking in various plists. I don't know where they are and I shouldn't have to know.
Possibly on Windows one can use IE to clear the cookies (but not credentials). Haven't tested it. On Mac, there is no such option. Clearing Safari certainly doesn't work.
What I've found is that with the credentials it is basically impossible to clear them. I've even tried making the web server deny access with unauthorised response, and Web Start still doesn't take the hint. It tries the credentials again automatically the next time whether you like it or not.
So in summary:
1) Java Web Start's tick box for storing credentials has no means to clear those credentials. Clearing all the Web Start Caches doensn't do the job.
2) Java Web Start's cookie store has no means to clear those cookies. Clearing all the Web Start Caches doesn't do the job.
What should happen:
Clearing the web start cache, at a bare minumum with javaws -uninstall should delete all credentials and cookies. There should also be something in the GUI that does it also.
REGRESSION : Additional Information
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Configure a web server to ask for CREDENTIALS before serving up a Web Start App. Enter username and password into the javaws login dialog. Tick the box to remember the credentials. Now there is no way to clear those credentials..
Configure a web server to send COOKIES before serving up a Web Start App. Now there is no way to clear those credentials..
Try clearing web start cache in Java Cache Viewer.
Try clearing web start cache from command line.
Neither have any effect on stored credentials or stored cookies.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Should be some mechanism to clear credentials
Should be some mechanism to clear cookies.
ACTUAL -
Credentials and cookies are stuck forever.
REPRODUCIBILITY :
This bug can be reproduced always.