Windows Native Authentication With 10gAS SSO Has Stopped Working: Client not found in Kerberos database
Last updated on JULY 01, 2016
Applies to:Oracle Application Server Single Sign-On - Version 10.1.2 to 10.1.4.3 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
***Checked for relevance on 04-OCT-2015***
10gAS environment has been running successfully with Windows Native Authentication (WNA) enabled SSO login for some time.
OC4J_SECURITY now fails to start and the OC4J_SECURITY log in $ORACLE_HOME/opmn/logs shows error 'Client not found in Kerberos database'.
Example OC4J~OC4J_SECURITY~default_island~1 log entries:
MIIS (Microsoft Identity Integration Server) has been configured on the Active Directory (AD) server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms