My Oracle Support Banner

WCC 11g: Kerberos and WNA Fail due to "Specified Version of Key is not Available" Exception (Doc ID 1505845.1)

Last updated on SEPTEMBER 16, 2019

Applies to:

Oracle WebCenter Content - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

With Kerberos configured, after clicking the Login button on the 11g Webcenter Content server login page, instead of going directly into the WCC main page, the WCC is prompting for authentication.

The WCC Managed Server log shows the following exception:

####<Nov 5, 2012 3:29:26 PM PST> <Debug> <SecurityAtn> <us01u354> <UCM_server1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1352158166569> <BEA-000000> <acceptGssInitContextToken failed
com.bea.security.utils.kerberos.KerberosException: Failure unspecified at GSS-API level (Mechanism level: Specified version of key is not available (44))
       at com.bea.security.utils.kerberos.KerberosTokenHandler.acceptGssInitContextTokenInDoAs(KerberosTokenHandler.java:334)
       at com.bea.security.utils.kerberos.KerberosTokenHandler.access$000(KerberosTokenHandler.java:41)
       at com.bea.security.utils.kerberos.KerberosTokenHandler$1.run(KerberosTokenHandler.java:227)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.