AD Passwordsync

We are planning to use AD passwordsync. Currently our AD accounts are linked to OIM identities based per the below reconciliation rule:
<OIM User ID> EQUALS <EmpNo attr on AD>
i.e the AD sAMAccountName is not same as the OIM user ID and sAMAccount is not stored on OIM user profile.
Per the AD passwordsync connector documentation, when password is changed on AD the sAMAccountName is passed onto OIM side and it is matched to the OIM user attribute mentioned during the connector installation (default attribute is 'Users.User ID'.
As mentioned in our case, sAMAccountName is not same as OIM User ID and is not stored on user profile. And we do only target source recon with AD.
How can we configure the passwordsync in our scenario?

Not.
You are not totally clear in what your environment is: is SAMAccountName empty, or just not the same?
If SAMAccountName is not set up properly, I fail to see why you would want to use password synchronisation. You will have to rework the SAMAccountName format issue first.

Similar Messages

Sun Java System Identity Manager 7.1 PasswordSync direct mode ERROR!

Hello,i wanna use direct mode to config the Sun Java System Identity Manager PasswordSync to avoid the complex configuration of JMS, but I get the following error in logs:
03/26/2008 10.52.34.062000 [2164] (../../../src/wps/passwordsync/lhpwic.cpp,591): EndpointURL: http://idmzone1.gmcc.net:8080/idm/servlet/rpcrouter2
03/26/2008 10.52.34.062000 [2164] (../../../../src/wps/agent/connect/RAEncryptor.cpp,69): RAEncryptor::Decrypt3DES: input length (16) moded to 2
03/26/2008 10.52.34.062000 [2164] (../../../src/wps/passwordsync/lhpwic.cpp,624): about to login...
03/26/2008 10.52.34.109000 [2164] (../../../src/wps/passwordsync/lhpwic.cpp,628): Login failed error code : -1072896682. Disassembing client
03/26/2008 10.52.34.109000 [2164] (../../../src/wps/passwordsync/lhpwic.cpp,648): Exit: GetClient
03/26/2008 10.52.34.109000 [2164] (../../../src/wps/passwordsync/lhpwic.cpp,916): Error getting our soap, bailing out.
It is really difficult to find the way to resolve this probblem..... PasswordSync direct mode works fine in 6.0 in my VM.. but error here in 7.1.
Is there anyone can give me a suggestion? Thanks you very much!

Tried Hot fix 81 also still giving me the error and re-rigisterd dotnet.dll
Log File for Hot fix 81
(../../../src/wps/passwordsync/lhpwic.cpp,559): Error reading dumpFileBase, no dump file generation on exception
(../../../src/wps/passwordsync/lhpwic.cpp,567): Exit: ReadRegistrySettings
(../../../src/wps/passwordsync/lhpwic.cpp,593): Soap client created
(../../../src/wps/passwordsync/lhpwic.cpp,594): ClientTimeout: 18000
(../../../src/wps/passwordsync/lhpwic.cpp,604): Proxy server not specified
(../../../src/wps/passwordsync/lhpwic.cpp,608): EndpointURL: http://idm-dev:80/idm/servlet/rpcrouter2
(../../../../src/wps/agent/connect/RAEncryptor.cpp,69): RAEncryptor::Decrypt3DES: input length (16) moded to 2
(../../../src/wps/passwordsync/lhpwic.cpp,641): about to login...
(../../../src/wps/passwordsync/lhpwic.cpp,645): Login failed error code : -2147467259. Disassembing client
(../../../src/wps/passwordsync/lhpwic.cpp,665): Exit: GetClient
(../../../src/wps/passwordsync/lhpwic.cpp,935): Error getting our soap, bailing out.
even if i gave wrong username and password it giving me the same error
Can someone help on this

AD PasswordSync - Direct mode workflow setup

Is there any information out there pertaining to setting up passwordSync in AD with IDM that goes into detail of how the process flows through each component? I'm looking for a more detailed explaination of IDM to gateway to AD to passSync back to IDM. Specifically:
- When passSync send the password back to IDM in direct mode, does IDM send it back to the AD resource? Why or Why not?
- If a load-balancer is in front of 2 gateways, what adverse effects will it have on IDM and AD? Why?
Thanks,
~idmNewbie
Edited by: rlewkowski on Mar 24, 2009 12:11 PM

- When passSync send the password back to IDM in direct mode, does IDM send it back to the AD resource? Why or Why not?
Answer : NO, this is default behavior of pass sync workflow
- If a load-balancer is in front of 2 gateways, what adverse effects will it have on IDM and AD? Why?
Answer : Gateways are not involved in Pass Sync Process itself, only if you have resources OTHER than AD, which are being managed via gateway.
BY the way - gateways can not work in active-active mode, this is not supported architecture. (only failover mode Active - Passive)

IDM 8.0 - Installing/Configuring PasswordSync on Windows DC

The admin guide describes how to install PasswordSync on the domain controllers through an msi for installing and an exe for configuring. Is there an automated way of performing these steps?
Thank you in advance

Hi,
Please type No when install asking for ACL (UTL_INADDR)

Install PasswordSync Servlet as a separate webapp from IdM

We run Identity Manager 8.1 on a RHEL5 server and have PasswordSync installed on our domain controllers running Windows 2000 server. We have configured PasswordSync to use JMS (Sun Glassfish Message Queue 4.4). However, the PasswordSync servlet is installed in the same container within the same webapp context as IdM. We would like to pull out the PasswordSync servlet into it's own webapp, served in either the same container as IdM or not, so that we can still queue password changes from AD during IdM maintenance (IdM application stopped). Has anyone had any experience with this set up?
According to the FAQ for Sun Java Identity Manager 8.1 (chapter 11), you can install the PasswordSync servlet on a different server from IdM and all you need is "...the spml.jar and idmcommon.jar jar files, in addition to any jar files required by the JMS application". However, after some trial and error, I've discovered that the idmclient.jar contains the PasswordSyncServlet class, so it's also required.
Thanks,
Eric

More on this effort... I have created a war containing the PasswordSync Servlet and deployed it to a separate instance of Tomcat. When I try to access the servlet path in my browser, I get the following error message:
"java.lang.IllegalStateException: Error initializing Encryptor: null"
There are no others errors in the Tomcat logs. Has anyone ran into this issue while setting up PasswordSync as a stand alone servlet?

Passwordsync Agent Configuration

Folks,
I need help on configuring "passwordsync agent (7.1 version)" / JMS Configuration / Others for IDM 7.1.
Anticipating help on same.
Thanks
Randhir Singh

Issue resolved. It's due to a aix bug, documented in
AGENT INSTALL ON AIX 6.1:ERROR IN INVOKING TARGET 'AGENT NMB NMO NMHS EMSUBAGENT' [ID 1298284.1]
One step missing that note is to include
export OBJECT_MODE=32
if you don't do that you will get message like fatal error while executing make command.
Thanks.
Regards,
Satheesh Shanmugam
http://borndba.com

Passwordsync Direct Method

Can some one guide me if we configure Passwordsync Direct Method which Workflow is going to trigger to update the passwords in different resources.
I belive that ,if we configure JMS adapter only The default Synchronize User Password workflow triggers and update the remaining resources

Change User Password
Regards,
Surinder

Help AD PasswordSync and JMSListener

Hi
We are trying to use the JMS listener with AD for password sync.
The AD is working fine and in the log we can see its trying to send the password sync over.
But in the IDM nothing happens.We have set trace enabled but see nothing.THe JMS Listener logs show not even an incoming request. In IDM interface when we test the JMS Listener it says Test Connection successful.
On the other hand we are using Glassfish and the Message Broker shows a client connection coming in.
How to turn on more debugging ?Has anyone faced this?Is there something wrong on our mappings.
AD Logs:
Enter: PwSyncClient::SendToServlet
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,58): Enter: PwSyncClientBase::CrackUrl+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,73): Cracking URL+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,81): server = xxxxxxx+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,82): resource = /idm/servlet/PasswordSync+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,83): port = xxxx+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,84): use secured connection = 0+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClientBase.cpp,106): Exit: PwSyncClientBase::CrackUrl+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClient.cpp,61): Connecting to xxxx.xxx.xxx on port xxxx+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClient.cpp,82): Resource is '/idm/servlet/PasswordSync?JNDIProperties=java.naming.factory.initial%3dcom.sun.jndi.fscontext.RefFSContextFactory%3bjava.naming.provider.url%3dfile%3a%2f%2f%2ftmp%2fidmtestjms&accountId=&clientEndpoint=WHALE&connectionFactory=sunPasswordFactory&direct=false&email=test.local%40xxxx&emailEndUser=false&jmsPassword=Teus%2fIXg%2bPk%3d&jmsUser=admin&password=&queueName=sunPasswordConnectorQueue&resourceAccountGUID=a068029d539f744d82327b5f76e0e195&resourceAccountId=CN%3dtestlocal2%2cOU%3dPeople%2cOU%3dAuth%2cDC%3dxxxx%2cDC%3dxxx&resourcePassword=vFeI490e5q%2bVFXp6Q%2f3QDA%3d%3d&resourcetype=Windows Active Directory&sessionType=LOCAL'+
+08/06/2012 10.09.58.450000 [3544] (.\PwSyncClient.cpp,106): SendToServlet: opening direct connection+
+08/06/2012 10.09.58.590000 [3544] (.\PwSyncClient.cpp,186): httpSendRequest succeeded+
+08/06/2012 10.09.58.590000 [3544] (.\PwSyncClient.cpp,301): Info flag 19 returned 200+
+08/06/2012 10.09.58.590000 [3544] (.\PwSyncClient.cpp,240): servlet contacted+
+08/06/2012 10.09.58.590000 [3544] (.\PwSyncClient.cpp,250): Exit: PwSyncClient::SendToServlet+
+08/06/2012 10.09.58.590000 [3544] (.\lhpwic.cpp,597): Got initialization mutex+
+08/06/2012 10.09.58.590000 [3544] (.\lhpwic.cpp,610): Released Mutex+
+08/06/2012 10.09.58.590000 [3544] (.\lhpwic.cpp,240): Exit: SyncPassword+
Broker Logs:
+[06/Aug/2012:10:22:53 PDT] [B1065]: Accepting: admin@xxxxxxxx->jms:33508. Count: service=1 broker=1+
+[06/Aug/2012:10:22:54 PDT] [B1066]: Closing: admin@xxxxxxxxx->jms:33508 because "[B0059]: Client closed the connection". Count: service=0 broker=0+

Did you try to set the trace as per the following:
http://docs.oracle.com/cd/E19225-01/820-7976/ahyej/index.html
Hope this helps.
==========
To Collect Logs for the Different Modes
PasswordSync trace logs are the same, whether you are using a direct access mode or JMS mode configuration. However, these trace logs might only provide partial information. You must configure different classes for each configuration to collect logs on the server side, as described in the following sections.
Tracing in Direct Mode
When using PasswordSync with a direct access mode configuration, the trace logs show failures, but not all logged failures are real failures. For example, in some circumstances the view check-in takes a long time, which shows as a failure in the log. You must trace on the server side to see this information.
In Direct mode, PasswordSync talks to the servlet that generates the view to be checked into the repository. You can trace the com.waveset.rpc.GenericMessageHandler class at level 4 to view all phases of password synchronization, from receiving the password change to the response generated and returned to the servlet. Level 4 is the only level that supplies enough detail for troubleshooting.
Tracing in JMS Mode
When using PasswordSync with a JMS mode configuration, the logs only show successful or failed deliveries to the JMS server. From this point on, you must rely on server side logs. JMS tracing is a little more complex.
You can trace the com.waveset.rpc.PasswordSyncHandler class at level 4 to convert the messages generated by the PasswordSync dll into a JMS message and add those messages to the JMS queue. Limited tracing is available in this class, and only level 4 can provide enough information to help with troubleshooting.
If PasswordSync successfully delivers the JMS message to the JMS queue, the tracing will not help you find the cause of a problem. The next, and final step is to trace the JMS adapter. See the Oracle Waveset 8.1.1 Resources Reference for instructions.

Configuring AD PasswordSync

Hi,
I need some help regarding AD PasswordSync.I have gone through the http://download.oracle.com/docs/cd/E19543-01/820-2954/820-2954.pdf (Sun™ Identity Manager 8.0 Administration)document.
I want to Configure PasswordSync with JMS Server. Presently I am using JBOSS application server.I want to do the JMS setup in JBOSS application server. The document describes how to do the JMS configuration in Sun JMS Server not with JBOSS application server.
It will be great if somebody provides me the steps for doing the same in JBOSS server.
Can any body provide me the sample data for The JMS Listener Resource Wizard “Resource Parameters” page.
Thank in advance..
Waiting eagerly for reply. :)

Hello,
In the documentation (P. 421) you will find all the PasswordSync info you need to set it up.
There is also the below note.
NOTE • The instructions in this section assume you have installed Sun Message
Queue. (The necessary tools are located in the bin/ directory of your
Message Queue installation.)
• You can use either the Message Queue administrative GUI (imqadmin)
or the command-line tool (imqobjmgr) to create these administered
objects. The following instructions use the command-line tool.
We use JMS 4.3, the documentation for setting this up may be found here:
http://download.oracle.com/docs/cd/E19879-01/820-6740/index.html
This should provide you with a good jumping off point.
IDMxml

PasswordSync Configuration - JMS Properties Settings

Hi,
I am basically trying to install and configure the password Sync process on a Windows 2000 Domain controller to interact with Sun IdM 6.0.
I had installed the .NET 1.1 framework required for a Windows 2000 Domain Controller and PasswdSync. Now when I am trying to configure the PasswordSync, I am not sure what values should be entered against the "java.naming.factory.initial" and "java.naming.provider.url" properties under the JMS Properties tab of the PasswordSync configuration wizard. Also, I would appreciate if any one of you could throw some light on JMS Settings as well. I have set-up the JMS server and created a connection factory required before trying to configure.
Thanks,
Indie.

Hi,
I put tcpmon proxy between windows pwsync and IDM to determine if the password update
was being sent and got the following:
==============
Listen Port: 8080
Target Host: 170.1.1.5
Target Port: 8080
==== Request ====
POST /idm/servlet/rpcrouter2 HTTP/1.0
Accept: text/*
SOAPAction: "urn:lighthouse"
Content-Type: text/xml; charset=utf-8
User-Agent: VCSoapClient
Host: 170.1.1.5:8080
Content-Length: 1165
Connection: Keep-Alive
Pragma: no-cache
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http:
//www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><soap:Body soap:encodingStyle="http://schemas.xmlsoap
.org/soap/encoding/"><snp:queuePasswordUpdate xmlns:snp="urn:lighthouse"><userEmailAddress>[email protected]</userEmailAddress><resourc
eAccountId>CN=Gabriela Castro,CN=Users,DC=domain,DC=net</resourceAccountId><resourceAccountGUID>889e54e67501944ab573934e4b2724d6</resourceA
ccountGUID><password>fr6j+8qxoHOqarRvYS8Flg==</password><accounts xsi:nil="1"/><resourcename xsi:nil="1"/><resourcetype>Windows Active Direc
tory</resourcetype><clientEndpoint>AFISERV23P</clientEndpoint><jmsUser>guest</jmsUser><jmsPassword>guest</jmsPassword><queueName>destQueue
</queueName><connectionFactory>destFactory</connectionFactory><sessionType>LOCAL</sessionType><JNDIProperties>java.naming.factory.initial=
com.sun.jndi.fscontext.RefFSContextFactory;java.naming.provider.url=file:///C:imq</JNDIProperties><singleResult>true</singleResult></snp:que
uePasswordUpdate></soap:Body></soap:Envelope>==== Response ====
HTTP/1.1 200 OK
X-Powered-By: Servlet/2.4
Content-Type: text/xml;charset=UTF-8
Date: Tue, 20 Nov 2007 22:23:05 GMT
Server: Sun-Java-System/Application-Server
Connection: close
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'
xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/1999/XMLSchema'>
<SOAP-ENV:Body>
<ns1:queuePasswordUpdateResponse
    xmlns:ns1='urn:lighthouse'
    SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
      <return xsi:type='xsd:string'>noIDMSessionRequired|ok|</return>
</ns1:queuePasswordUpdateResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
==============from which I saw that java.naming.provider.url specifies a windows path and not a unix path, and since
IDM is installed in UNIX (the servlet which is invoked by pwsync) this is what was failing, I changed it to the actual unix path where the .bindings file
is and it worked.
I can�t recall what I read in the documentation but it is not clear the value that this parameter must have,
it specifies what the parameter is but when using both unix and windows environments it gets confusing, at least for me,
but anyway, it works now.

PasswordSync -direct mode normalize Exception

Hey, I am getting this strange exception while resetting AD user's password.
Does anyone seen this before?
Environment Info:
Sun Identity Management 8.1
Active Directory 2008 64-bit.
User's resourceAccountId=CN=Xx Yy,OU=OU ou1,OU=OU ou2,OU=OU ou3,OU=OU ou4,OU ou5,DC=lab,DC=net,DC=il
http-80-2(0x0162e703) RFC2253Parser#normalize() Catch com.sun.idm.util.ldap.InvalidDnException: Invalid character found in sequence starting at position 0
     at com.waveset.util.WavesetException.checkBreakpoint(WavesetException.java:488)
     at com.waveset.util.WavesetException.<init>(WavesetException.java:109)
     at com.sun.idm.util.ldap.InvalidDnException.<init>(InvalidDnException.java:38)
     at com.sun.idm.util.ldap.DnUtil.parse(DnUtil.java:192)
     at com.sun.idm.util.ldap.DnUtil.normalize(DnUtil.java:103)
     at com.waveset.util.RFC2253Parser.normalize(RFC2253Parser.java:99)
     at com.waveset.util.Util.normalizeString(Util.java:4164)
     at com.waveset.rpc.GenericMessageHandler.compareAccountIds(GenericMessageHandler.java:3407)
     at com.waveset.rpc.GenericMessageHandler.findSourceResource(GenericMessageHandler.java:3385)
     at com.waveset.rpc.GenericMessageHandler.syncUserPassword(GenericMessageHandler.java:2496)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.waveset.rpc.GenericMessageHandler.request(GenericMessageHandler.java:367)
     at com.waveset.rpc.DirectPasswordSync.doPasswordSync(DirectPasswordSync.java:75)
     at com.waveset.rpc.PasswordSyncServlet.doGet(PasswordSyncServlet.java:92)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at com.sun.idm.profiler.instrumentation.RequestTimingFilter.doFilter(RequestTimingFilter.java:76)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
     at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:151)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
     at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
     at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
     at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
     at java.lang.Thread.run(Unknown Source)

- When passSync send the password back to IDM in direct mode, does IDM send it back to the AD resource? Why or Why not?
Answer : NO, this is default behavior of pass sync workflow
- If a load-balancer is in front of 2 gateways, what adverse effects will it have on IDM and AD? Why?
Answer : Gateways are not involved in Pass Sync Process itself, only if you have resources OTHER than AD, which are being managed via gateway.
BY the way - gateways can not work in active-active mode, this is not supported architecture. (only failover mode Active - Passive)

PasswordSync with a Sun JMS Server: javax.jms.QueueConnectionFactory

Hi,
I have installed Sun IDM 8.1 and Sun DSEE7 and uses Active Directory as source for identities.
I then added a resource for the JMS Listener, but when I tried to do Test Connection I got this message:
Test connection failed for resource:
java.lang.ClassCastException: com.sun.messaging.ConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory
Can anybody help me with this.
rgds
Crimson
Edited by: Crimson on May 3, 2010 4:46 AM

Hi Sean,
it's better to ask this question at Sun Java System Messaging Server forum:
http://swforum.sun.com/jive/forum.jspa?forumID=15

Passwordsync direct method giving error 'already locked by 'Configurator''

Hi idm Gurus
When I am changing the user password from Idm Admin interface user receiving the pwsync failure email and notifying 'com.waveset.exception.LockedByAnother: Item User:35365 already locked by 'Configurator''
where as password successfully changed for the user
Is there any way that I can eliminate to get this error message to user?
Please help me.

Hi idm Gurus
When I am changing the user password from Idm Admin interface user receiving the pwsync failure email and notifying 'com.waveset.exception.LockedByAnother: Item User:35365 already locked by 'Configurator''
where as password successfully changed for the user
Is there any way that I can eliminate to get this error message to user?
Please help me.

PasswordSync Unexpected Broker Exception: [destroyed Connection]

DEBUGHIGH set on brokerd
metrics set to 60 on brokerd
Help appreciated.
15/Mar/2007:12:14:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30476096 free) Threads: 2 (14-1010)
In: 1 msgs (728 bytes) 14 pkts (2386 bytes)
Out: 0 msgs (0 bytes) 14 pkts (2795 bytes)
Rate In: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (0 bytes/sec)
[15/Mar/2007:12:15:28 PDT] Received JMQRBufferSize -100
[15/Mar/2007:12:15:28 PDT] [B1065]: Accepting: [email protected]:39174->jms:39104. Count=1
[15/Mar/2007:12:15:28 PDT] Created new session 1984136176305554944 on connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Creating new Producer 1984136176305558016 on Q:myTestQueue for connection 1984136176305549056
[15/Mar/2007:12:15:28 PDT] Producer Producer[1984136176305558016,Q:myTestQueue,1984136176305549056] is true
[15/Mar/2007:12:15:28 PDT] Cleaning up transactions on connection IMQConn[CLOSED,[email protected]:39174,jms:39104]
[15/Mar/2007:12:15:28 PDT] closed connection IMQConn[DESTROYING,[email protected]:39174,jms:39104]:
java.io.IOException: [B4117]: Unexpected Broker Exception: [destroyed Connection]
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.writeData (IMQConnection.java:1930)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:803)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java :141)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
at java.lang.Thread.run(Thread.java:595)
[15/Mar/2007:12:15:28 PDT] [B1066]: Closing: [email protected]:39174->jms:39104 because "[B0059]: Client closed the connection". Count=0
[15/Mar/2007:12:15:47 PDT]
Connections: 0 JVM Heap: 33226752 bytes (30083968 free) Threads: 2 (14-1010)
In: 2 msgs (1632 bytes) 28 pkts (4949 bytes)
Out: 0 msgs (0 bytes) 28 pkts (5590 bytes)
Rate In: 0 msgs/sec (15 bytes/sec) 0 pkts/sec (42 bytes/sec)
Rate Out: 0 msgs/sec (0 bytes/sec) 0 pkts/sec (46 bytes/sec)

Hi Tom,
Thanks for the quick response!
I am glad to hear that the log level is the reason for the output and not an issue with the broker!
Thanks again....
-Howard

Password Sync Connector Error 11gR2

Hi all,
I am using following products
IDM 11.1.2.0,
activedirectory-11.1.1.5.0 connector with Patch P14190610_111150_Generic.
MSFT_PSync_91150 for Password Sync.
Please let me know that AD Password Sync Connector 9.1.1.5 can be configured with OIM *11gR2* ?
Because I am getting error *"Password updation failed in child process "* I have used the same connector with OIM 11.1.1.5.0 (11gR1) and it was working fine. do i need to make any changes / settings in the OIM for AD Resource also?
Thanks

thanks for your reply,
Please can you help me on the following ....
I have installed AD PasswordSync Connector 9.1.1.5.0 (MSFT_AD_PSync_9.1.1.5.0) with newly released patch MSFT_AD_PSync_9.1.1.5.6 (patch 14627510). I am getting error that Password updation failed in child process
its not making any sence as the same connector was working fine with 11gR1. I have uninstalled and reconfigured the connector but no luck.
Can you through some light on it?
what i think that there is some communication issue between IDM and AD server, I have check the communication and found no issue. is it that SSL is compulsory for this connector although its not mentioned in any of the document.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ebug [10/09/12 14:09:27] Inside sgsloidi::setParameters
Debug [10/09/12 14:09:27] The SOAP start element is
Debug [10/09/12 14:09:27] <processRequest xmlns=""><sOAPElement>
Debug [10/09/12 14:09:27] The SOAP end element is
Debug [10/09/12 14:09:27] </sOAPElement></processRequest>
Debug [10/09/12 14:09:27] The path is
Debug [10/09/12 14:09:27] /spmlws/OIMProvisioning
Debug [10/09/12 14:09:27] End of sgsloidi::setParameters
Debug [10/09/12 14:09:27] Begin function sgsloidi::queryADUserAttribute()
Debug [10/09/12 14:09:27] Inside sgsladac c-tor
Debug [10/09/12 14:09:27] AD Host
Debug [10/09/12 14:09:27] 172.20.20.135
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] AD Port
Debug [10/09/12 14:09:27] 389
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] AD Base DN
Debug [10/09/12 14:09:27] DC=YYYt,DC=vvv,DC=www
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] Inside ConnectToADSI
Debug [10/09/12 14:09:27]
ADSI Bind success full
Debug [10/09/12 14:09:27] Begin function sgsladac::searchAttrValue()
Debug [10/09/12 14:09:27] [Base DN : DC=yyy,DC=vvv,DC=www]; [Filter : (&(objectClass=user)(samAccountName=IDM005))]; [Attribute : samAccountName]
Debug [10/09/12 14:09:27] Search success with one result.
Debug [10/09/12 14:09:27] End function sgsladac::searchAttrValue()
Debug [10/09/12 14:09:27] End function sgsloidi::queryADUserAttribute()
Debug [10/09/12 14:09:27] Inside sgsladac destructor
Debug [10/09/12 14:09:27] <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>Unknown method</faultstring></env:Fault></env:Body></env:Envelope>
Debug [10/09/12 14:09:27] Inside sgsloidiOIMGeneralErrorHandler
Debug [10/09/12 14:09:27] Unable to update IDM005. There are error messages in the searchReponse. Please check log for details
Debug [10/09/12 14:09:27] Inside sgsladds::sgslperwriteData YOOOO
Debug [10/09/12 14:09:27] Inside sgsladac c-tor
Debug [10/09/12 14:09:27] AD Host
Debug [10/09/12 14:09:27] 172.20.20.135
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] AD Port
Debug [10/09/12 14:09:27] 389
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] AD Base DN
Debug [10/09/12 14:09:27] DC=yyy,DC=vvv,DC=www
Debug [10/09/12 14:09:27]
Debug [10/09/12 14:09:27] Only dataattribute
Debug [10/09/12 14:09:27] Got Registry enteries
Debug [10/09/12 14:09:27] contact
Debug [10/09/12 14:09:27] description
Debug [10/09/12 14:09:27] Got Entiredn
Debug [10/09/12 14:09:27] OU=oimpwdsyncmoetest.gov.kw,ou=OIMADPasswordSync,DC=yyy,DC=vv,DC=wwww
Debug [10/09/12 14:09:27] Encrypted record already exists in Datastore
Debug [10/09/12 14:09:27] Already Exists
Debug [10/09/12 14:09:27] Encrypted record already exists in Datastore
Debug [10/09/12 14:09:27] Already Exists
Debug [10/09/12 14:09:27] Inside sgsladdsSearchUser
Debug [10/09/12 14:09:27] Firing Search Request
Debug [10/09/12 14:09:27] AD search for a user objectGUID is successfull
Debug [10/09/12 14:09:27] Count success
Debug [10/09/12 14:09:27] Search result fetched
Debug [10/09/12 14:09:27] 0:430 6 314 420 AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAn+Kii3Krv0GOKE3aE8a/vwAAAAAmAAAAUABhAHMAcwB3AG8AcgBkACAARQBuAGMAcgBwAHQAaQBvAG4AAAAQZgAAAAEAACAAAADVc9Vqwy5JzRFSKTMKlZcowXUmtY/Giw1nYgIz01HZQgAAAAAOgAAAAAIAACAAAADnr10j8OQlKm35BMRt7yKNNQYNeR2JRPMQrlWheBs3XUAAAAB6it/wjG20tJgo5T9euni2Jldb/agmY5RDsoKVpvLnHAkptSd4OUIIaysGAWkqfv9iK69FtzUuh+DcmgkdSLtOQAAAAGMpkx8yFJaKXwnzoCZyElCZbrzdg5f3GNj+S56lk4/UpVij9hFk5VeysObVw21NClzmGnuiBRtO+WF+LzChEUM=
Debug [10/09/12 14:09:27] --------------------&&&----------------
Debug [10/09/12 14:09:27] Inside sgsladds::sgsladdsgetData NEW Look
Debug [10/09/12 14:09:27] 0:430 6 314 420 AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAn+Kii3Krv0GOKE3aE8a/vwAAAAAmAAAAUABhAHMAcwB3AG8AcgBkACAARQBuAGMAcgBwAHQAaQBvAG4AAAAQZgAAAAEAACAAAADVc9Vqwy5JzRFSKTMKlZcowXUmtY/Giw1nYgIz01HZQgAAAAAOgAAAAAIAACAAAADnr10j8OQlKm35BMRt7yKNNQYNeR2JRPMQrlWheBs3XUAAAAB6it/wjG20tJgo5T9euni2Jldb/agmY5RDsoKVpvLnHAkptSd4OUIIaysGAWkqfv9iK69FtzUuh+DcmgkdSLtOQAAAAGMpkx8yFJaKXwnzoCZyElCZbrzdg5f3GNj+S56lk4/UpVij9hFk5VeysObVw21NClzmGnuiBRtO+WF+LzChEUM=
Debug [10/09/12 14:09:27] Encoded Data Extracted in sgsladdsgetData
Debug [10/09/12 14:09:27] 430 6 314 420 AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAn+Kii3Krv0GOKE3aE8a/vwAAAAAmAAAAUABhAHMAcwB3AG8AcgBkACAARQBuAGMAcgBwAHQAaQBvAG4AAAAQZgAAAAEAACAAAADVc9Vqwy5JzRFSKTMKlZcowXUmtY/Giw1nYgIz01HZQgAAAAAOgAAAAAIAACAAAADnr10j8OQlKm35BMRt7yKNNQYNeR2JRPMQrlWheBs3XUAAAAB6it/wjG20tJgo5T9euni2Jldb/agmY5RDsoKVpvLnHAkptSd4OUIIaysGAWkqfv9iK69FtzUuh+DcmgkdSLtOQAAAAGMpkx8yFJaKXwnzoCZyElCZbrzdg5f3GNj+S56lk4/UpVij9hFk5VeysObVw21NClzmGnuiBRtO+WF+LzChEUM=
Debug [10/09/12 14:09:27] Moving out sgsladdsgetData
Debug [10/09/12 14:09:27] Encoded Data Extracted
Debug [10/09/12 14:09:27] 430 6 314 420 AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAn+Kii3Krv0GOKE3aE8a/vwAAAAAmAAAAUABhAHMAcwB3AG8AcgBkACAARQBuAGMAcgBwAHQAaQBvAG4AAAAQZgAAAAEAACAAAADVc9Vqwy5JzRFSKTMKlZcowXUmtY/Giw1nYgIz01HZQgAAAAAOgAAAAAIAACAAAADnr10j8OQlKm35BMRt7yKNNQYNeR2JRPMQrlWheBs3XUAAAAB6it/wjG20tJgo5T9euni2Jldb/agmY5RDsoKVpvLnHAkptSd4OUIIaysGAWkqfv9iK69FtzUuh+DcmgkdSLtOQAAAAGMpkx8yFJaKXwnzoCZyElCZbrzdg5f3GNj+S56lk4/UpVij9hFk5VeysObVw21NClzmGnuiBRtO+WF+LzChEUM=
Debug [10/09/12 14:09:27] Incrementing the MAX_RETRY LIMIT:
Debug [10/09/12 14:09:27] 1
Debug [10/09/12 14:09:27] numretries ======
Debug [10/09/12 14:09:27] 1
Debug [10/09/12 14:09:27] Inside sgslcodsupdateChild
Debug [10/09/12 14:09:27] 1:430 6 314 420 AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAn+Kii3Krv0GOKE3aE8a/vwAAAAAmAAAAUABhAHMAcwB3AG8AcgBkACAARQBuAGMAcgBwAHQAaQBvAG4AAAAQZgAAAAEAACAAAADVc9Vqwy5JzRFSKTMKlZcowXUmtY/Giw1nYgIz01HZQgAAAAAOgAAAAAIAACAAAADnr10j8OQlKm35BMRt7yKNNQYNeR2JRPMQrlWheBs3XUAAAAB6it/wjG20tJgo5T9euni2Jldb/agmY5RDsoKVpvLnHAkptSd4OUIIaysGAWkqfv9iK69FtzUuh+DcmgkdSLtOQAAAAGMpkx8yFJaKXwnzoCZyElCZbrzdg5f3GNj+S56lk4/UpVij9hFk5VeysObVw21NClzmGnuiBRtO+WF+LzChEUM=
Debug [10/09/12 14:09:27]
Encrypted record data updated successfully
Debug [10/09/12 14:09:27] Inside sgsladac destructor
Debug [10/09/12 14:09:27] End of sgsloidiOIMGeneralErrorHandler
Debug [10/09/12 14:09:27] Password updation failed in child process
Debug [10/09/12 14:09:27]
Relaxing while processing records from datastore
Debug [10/09/12 14:09:29]
About to UNBIND datastore after processing the Records
Debug [10/09/12 14:09:29]
Deleting datastore object pointer
Debug [10/09/12 14:09:30] Datastore --- Connect to AD
Debug [10/09/12 14:09:30]

AD Passwordsync

Similar Messages

Maybe you are looking for