Unable to login to OAM console after OIM integration Jump to sectionSymptomsCauseSolution After OAM-OIM integration, you might face issues with OAM console authentication using ‘oamadmin’ ID. Symptoms Authentication failure on OAM console (http://hostname:14100/oamconsole) Below error in OAM Weblogic logs [URI: /oamconsole/faces/login.jspx] Remote Server Failure:dev.oam.bbc.local:389.[[javax.naming.NoPermissionException: [LDAP: error code 50 – Insufficient Access Rights]; remaining name ‘cn=Users,dc=company,dc=com’Cause During OAM-OIM integration, OIDAuthenticator is added to Weblogic security realms and the principal for this authenticator is set as “uid=oamLDAP,cn=users,cn=company,dc=com” The permission issue is not with the “oamadmin” ID used to login to OAM console, it is with the access permissions of the ID used in OIDAuthenticator. In this case “oamLDAP” Solution Add “oamLDAP” or whatever is the ID used as principal in OIDAuthenticator to OIMAdministrators & OAMAdministrators group Once this is done you should be able to login to OAM console without any issues. Prasad Domala2016-12-08T18:20:43+00:00 Found the post helpful ? Please share it. FacebookTwitterLinkedInRedditGoogle+TumblrPinterestVkEmail About the Author: Prasad Domala I am a Senior Cloud Professional specialized in AWS Cloud with 11 years of IT experience. I am enthusiastic about Serverless Architecture. I am an expert in Oracle Fusion Middleware.