Hi. We are attempting to use java authentication with our j2ee application, but we are experiencing two problems which have already been lodged as bugs in openjdk upstream. http://bugs.sun.com/view_bug.do?bug_id=6979329 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6815182 They have been fixed in java7, but we would like to get these fixes backported into java6 and shipped as an errata so that kerberos authentication works. At the moment we have to run our own patched jvm (using patches from the commits against the issues above) but would like to move back to a rhel supported package
Graeme, is there a testcase for this that I can try?
Hi Deepak, Is there anything wrong with using the SpnegoReqFlags test case at http://hg.openjdk.java.net/jdk7/tl/jdk/rev/9d5cce463fa0 ? Regards, Graeme
Hi Graeme, Unfortunately not. That test requires importing an additional changeset in the first place (that added the kerberos testframework): http://hg.openjdk.java.net/jdk7/build-gate/jdk/rev/3f051f3ba5bb But even with that imported, the test still does not run with OpenJDK6. I suspect it relies on things working in a certain manner (OpenJDK7). I am still looking into it, but if I cannot find a solution, I am going to request a backout of that test.
Hi Graeme. Any further info on this?
Hi, Unfortunately I'm not quite sure what more information I can provide here to help. I'm not a java programmer (just a sysadmin), and these issues were noticed when one of our developers was trying to use JBoss Enterprise Portal Platform. If you want I can talk to the developer and see if they can look at writing up some test cases for you, but that will need some time to do that. Is there no other way we can move this forward seeing as the fixes are already in jdk7? Regards, Graeme
Hi Graeme. I can push it in IcedTea, but I think it would be nice to be able to ensure that the patch fixes what we want. Can you please add the JBoss dev to cc: if you don't mind?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0099.html