-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA
-
java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160427_1620_B301573
JIT - tr.r14.java.green_20160329_114288
GC - R28_Java8_SR3_20160427_1620_B301573_CMPRSS
J9CL - 20160427_301573)
JCL - 20160421_01 based on Oracle jdk8u91-b14java -version java version "1.8.0" Java(TM) SE Runtime Environment (build pxa6480sr3-20160428_01(SR3)) IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160427_301573 (JIT enabled, AOT enabled) J9VM - R28_Java8_SR3_20160427_1620_B301573 JIT - tr.r14.java.green_20160329_114288 GC - R28_Java8_SR3_20160427_1620_B301573_CMPRSS J9CL - 20160427_301573) JCL - 20160421_01 based on Oracle jdk8u91-b14
With http://www-01.ibm.com/support/docview.wss?uid=swg1IV82679 ibm java introduced throwing exception when keytab does not include configured principal [1]. Then EAP responds with 403 Forbidden response. And not expecting/standard 401 Unauthorized response to give a chance for client for selecting fallback mechanism for example.