OIM 10g Issue: LDAP: error code 49
Came across this error log when trying to integrate AD with OIM 10g
<Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <====================================================> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController : connectToAvailableAD : Authentication Error Occur[LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece]> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <==================================================== > <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <====================================================> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController : connectToAvailableAD : The error occured in tcADUtilLDAPController::connectToAvailableAD():[LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece]> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <==================================================== >
<Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <====================================================> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController : searchResultPageEnum : [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece]> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <==================================================== > <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <================= Start Stack Trace =======================> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController : searchResultPageEnum> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <[LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece]> <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <Description : [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece]>
<Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.exception.ConnectionException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 773, vece] at com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.connectToAvailableAD(Unknown Source) at com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.searchResultPageEnum(Unknown Source) at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.performReconciliation(Unknown Source) at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.execute(Unknown Source) at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.execute(SchedulerBaseTask.java:384) at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:164) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529) > <Jan 31, 2011 3:01:22 PM EST> <Error> <OIMCP.ADCS> <BEA-000000> <================= End Stack Trace =======================>
SOLUTION
You need ldapbp.jar. Put this in ThirdParty folder
xellerate\ThirdParty
See the AD doc. It will give u link to download it. 2.2.1.3 Copying the ldapbp.jar File. The ldapbp.jar file is used by the connector to enable LDAP-based search of user records on the target system. You must download this file from the Sun Web site and copy it into the ThirdParty directory as follows:
- 1. Log on the Sun Web site at http://java.sun.com/products/jndi/downloads/index.html
- 2. Click Download JNDI 1.2.1 & More.
- 3. From the table on the page that is displayed, select and download the ldap-1_2_4.zip file.
- 4. Extract the contents of the ZIP file and copy the ldapbp.jar file from the lib directory to the OIM_HOME/xellerate/ThirdParty directory.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
February 6, 2020
Created by: Daniel Redfern
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
February 24, 2019
Created by: Daniel Redfern
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
August 7, 2018
Created by: Daniel Redfern
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date