Login to ODI Studio Fails With "ODI-10199: Incorrect ODI username or password" When External Authentication is Used On Microsoft Active Directory Via SSL

(Doc ID 2324702.1)

Last updated on NOVEMBER 09, 2017

Applies to:

Oracle Data Integrator - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Switching Oracle Data Integrator (ODI) 12c Studio to External Authentication, in both SSL and Non-SSL modes is successful and Microsoft Active Directory (AD) accounts are visible.

However:

Following message is received when SSL is used:

oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
Run into error oracle.igf.ids.IDSException: Operations error: entity=<ENTITY>,DC=<DC>,DC=<DC> op=find mesg= while using identity store.
  at oracle.odi.core.security.internal.ODIJpsHelper.translateNativeSecurityException(ODIJpsHelper.java:201)
  ...
Caused by: oracle.ods.virtualization.service.VirtualizationException: oracle.ods.virtualization.engine.util.DirectoryException: LDAP Error 2 : simple bind failed: <FULLY QUALIFIED HOSTNAME>:636
  at oracle.ods.virtualization.operation.SearchOperation.process(SearchOperation.java:209)
  at oracle.ods.virtualization.operation.SearchOperation.process(SearchOperation.java:47)
  at oracle.ods.virtualization.service.DefaultVirtualizationSession.processOperation(DefaultVirtualizationSession.java:403)
  at oracle.ods.virtualization.service.DefaultVirtualizationSession.search(DefaultVirtualizationSession.java:190)
  at com.oracle.ovd.arisid.OvdIdsStackProvider.doFind(OvdIdsStackProvider.java:1326)
  ... 188 more
Caused by: oracle.ods.virtualization.engine.util.DirectoryException: LDAP Error 2 : simple bind failed: <FULLY QUALIFIED HOSTNAME>:636
  at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getLDAPContext(BackendJNDI.java:1164)
  at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getConnection(BackendJNDI.java:1027)
  at ...
Caused by: javax.naming.CommunicationException: simple bind failed: XXXX.XXXXX.com:636 [Root exception is java.net.SocketException: Connection reset]
  at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:219)
  at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2788)
  at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)
  at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
  at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
  at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
  at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)
  at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
  at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
  at javax.naming.InitialContext.init(InitialContext.java:244)
  at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:154)
  at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.createCtx(JNDIConnectionPool.java:648)
  at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.create(JNDIConnectionPool.java:680)
  at oracle.ods.virtualization.engine.backend.jndi.JNDIConnectionPool.(JNDIConnectionPool.java:216)
  at oracle.ods.virtualization.engine.backend.jndi.RemoteServer.getJNDIConnectionPool(RemoteServer.java:182)
  at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.getLDAPContext(BackendJNDI.java:1085)
  ... 229 more
Caused by: java.net.SocketException: Connection reset
  at java.net.SocketInputStream.read(SocketInputStream.java:210)
  at ...

Changes

 

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