My Oracle Support Banner

Troubleshooting The Connector For WebSphere - Oracle Access Manager (OAM) 10.1.4 (Doc ID 402877.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Identity - Version: 10.1.4 and later   [Release: 10g and later ]
COREid Access - Version: 10.1.4 to 10.1.4.3.0]
Information in this document applies to any platform.
Checked for relevance on 11-Apr-2010

Goal

The purpose of this note is to highlight Troubleshooting the Connector for WebSphere Integration Issues of Oracle Access Manager (OAM) 10.1.4 that were reported in our integration guide so that those issues would be more visible and searchable through our website https://support.oracle.com.

This note is part of the following Master Note:
<> Master Note: Troubleshooting Integration Issues - Oracle Access Manager (OAM) 10.1.4

Solution

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
  Goal
  Solution
     Troubleshooting the Connector for WebSphere
     1.    Error When Searching Users or Groups Using WAS Role Mapping
     2.    WebSphere 5 Server Does Not Start
     3.    Signature Not Available Error
     4.    All The Jars Are Not In ClassPath: NoClassDefException
     5.    SSLPeerUnverifiedException-Peer Not Authenticated Exception
     6.    ObConfig.NO_CONFIG_FILE
     7.    UnsatisfiedLinkError
     8.    NoClassDefFound error ..ObAccessException
     9.    ObSSOCookie Is Not Set
     10.    WebPass Is Rejecting ObSSOCookie
     11.    WebGate Is Rejecting ObSSOCookie
     12.    IdentityXML Calls Fail With an Unauthorized Exception
     13.    "Server Specific Error 10" While Restarting the WebSphere Administrative Server
     14.    CustomRegistryException
     15.     Error making SOAP request java.io.FileNotFoundException:http://cobalt.oblix.net:80/identity/oblix/apps/userservcenter/bin/ userservcenter
     16.    Error making SOAP request java.io.IOException: Server returned HTTP response code: 401
     17.    InvalidUserRegistryConfigException: User [username] not authenticated"
     18.    StringIndexOutOfBoundsException: String index out of range
     19.    Portal Server allow logins with old passwords  
     20.    Deactivated Oracle Access Manager user can still access WebSphere resources
     21.    WebSphere Portal Server not come up, resulting in security exceptions
     22.    Single sign-on is not working when a URL resource is protected with a Basic Over LDAP authentication scheme, even though TAI is enabled.
     23.    ORBA.TRANSACTION_ROLLEDBACK: minor code
     24.     Initializer W SECJ0007E: Error during security initializationjava.lang.NullPointerException
     25.     Security Error: Either username/password is wrong or this user is not authorized to connect to admin server
     26.     Not Authorized error when Trying To Access a WAS resource or a WebSphere Portal resource
     27.     TAI Is Failing
     28.  Error in the TAI logs: Error no action found  
     29.     WAS Registrytester.bat may fail  
     30.     Unable to search users in the WebSphere Portal Admin page.  
     31.     IBM WebSphere Portal Server gives an error "No Portlets to display"  

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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