WNA Error - Found unsupported keytype (18) for HTTP/dev.loginxxx@xxx.com (Doc ID 2119015.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.2.3.4 and later
Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.

Symptoms

WNA is not working. When set to collect more details using -Dsun.security.krb5.debug=true -Dsun.security.spnego.debug=true to the JAVA PROPERTIES shows following errors.

Java config name: /apps/xxxx/krb5.conf
Loaded from Java config
Added key: 17version: 8
Found unsupported keytype (18) for HTTP/dev.login.xxxx.com@xxxxCOM <<<<< error
Added key: 23version: 8
Added key: 3version: 8
Added key: 1version: 8
Ordering keys wrt default_tkt_enctypes list
Using builtin default etypes for default_tkt_enctypes
default etypes for default_tkt_enctypes: xx xx 23 1 3.
>>> KdcAccessibility: reset
Added key: 17version: 8
Found unsupported keytype (18) for HTTP/dev.login.xxxxx.com@xxxx.COM <<<<< error
Added key: 23version: 8
Added key: 3version: 8
Added key: 1version: 8
Ordering keys wrt default_tkt_enctypes list
Using builtin default etypes for default_tkt_enctypes
default etypes for default_tkt_enctypes: 17 16 23 1 3.
Using builtin default etypes for default_tkt_enctypes
default etypes for default_tkt_enctypes: 17 16 23 1 3.
>>> KrbAsReq creating message
>>> KrbKdcReq send: kdc=xxxxx TCP:88, timeout=3000, number of retries =3, #bytes=173
>>> KDCCommunication: kdc=xxxxx TCP:88, timeout=3000,Attempt =1, #bytes=173
>>>DEBUG: TCPClient reading 270 bytes

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms