PH57364: WHEN CLIENTS SET UP SPNEGO, THEY OFTEN CONFIGURE KERBEROS INSTEAD (AND SET KERBEROS AND LTPA), BUT THIS ENDS UP BREAKING SPNEGO

APAR status

• Closed as program error.

Error description

• "SPNEGO web authentication" validation fails even when the
  correct values are entered.
  
  When a user encounters this issue, the error includes the
  kerberos validation error message on a JAAS Subject that
  starts with "WAS/". If it were SPNEGO validation, the JAAS
  Subject would start with "HTTP/"
  
  -- Sample error --
  org.ietf.jgss.GSSException, major code:13, minor code: 0 major
  string: Invalid credentials minor string:
  Cannot get credential from JAAS Subject for principal:
  WAS/testserer.ibm.com@IBMDOMAIN
  -------------------
  

Local fix

• Manually edit security.xml
  
  - take backup of security.xml
  -edit the krb5Config, krb5Keytab, by removing value, edit
  krb5Spn="HTTP/${HOST}" with krb5Spn="WAS/${HOST}" and remove tag
  line -->  configured="true"
  -save the file
  
  
  krb5Config="/root/recreate/spnego/new_mikenoupn.conf"
  krb5Keytab="/root/recreate/spnego/new_mikenoupn.keytab"
  krb5Spn="HTTP/${HOST}" trimUserName="true"
  enabledGssCredDelegate="true" configured="true"/>
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  who configured Kerberos Authentication.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: "SPNEGO web authentication" validation  *
  *                      fails even when the correct values are  *
  *                      entered.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Once "Kerberos configuration" has been saved, "Kerberos and
  LTPA"
  authentication mechanism stays enabled.
  As a result, "SPNEGO web authentication" validation checks both
  Kerberos and SPNEGO configuration.
  Even when the correct values are entered in the SPNEGO web
  authentication panel, the panel fails to save the configuration
  due to the unnecessary validation on the Kerberos
  configuration.
  

Problem conclusion

• This APAR introduces a new AdminTask command:
  unconfigureKrbAuthMechanism()" to reset the authentication
  mechanism from "Kerberos and LTPA" to "LTPA" while preserving
  the
  configured values in the Kerberos authentication for later use.
  
  -- usage example --
  >wsadmin -username xxx -password yyy -lang jython
  wsadmin>AdminTask.unconfigureKrbAuthMechanism()
  wsadmin>AdminConfig.save()
  -------------------
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.20 and 8.5.5.26.
  For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels