PWSync not working on one node

This topic has 0 replies, 1 voice, and was last updated 2 months, 1 week ago by [email protected].

  • Author
    Posts
  • #27417

    Hello

    I’ve 2 ec2 instances and each instance has openidm (4.0.0) and opendj (3.0.0) installed.
    I’ve password plugin installed as well.
    Also have same configuration for both of the instances.
    While I’m testing this plugin, if I modify the password on opendj of instance 2, it propagates the change to its own idm and then implicitely sync with the opendj of instance1.
    However, if I modify password on opendj of instance 1, it doesn’t propagate the change to idm of instance 1. Hence instance 2 still has old password.
    I checked instance 1’s audit/sync.csv, there is no logs.
    I also have enabled the debuging and see following message –

    
    [22/Jan/2020:10:27:59 -0500] 38 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={handleStatusNotification(OpenidmAccountStatusNotificationHandler.java:500)} Received notification for user: uid=test.sachin,dc=ihsmhosting,dc=com
    [22/Jan/2020:10:27:59 -0500] 39 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={handleStatusNotification(OpenidmAccountStatusNotificationHandler.java:524)} Adding end user attribute value 59bf6780-a608-42d6-8630-bdf89dbb4cc1 from attr entryUUIDto notification
    [22/Jan/2020:10:27:59 -0500] 40 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={handleStatusNotification(OpenidmAccountStatusNotificationHandler.java:524)} Adding end user attribute value test.sachin from attr uidto notification
    [22/Jan/2020:10:27:59 -0500] 41 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={processOpenIDMNotification(OpenidmAccountStatusNotificationHandler.java:606)} User uid=test.sachin,dc=ihsmhosting,dc=com 's password reset to : [Welcome4]. Additional data: {entryUUID=[59bf67
    80-a608-42d6-8630-bdf89dbb4cc1], uid=[test.sachin]}
    [22/Jan/2020:10:27:59 -0500] 42 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={processOpenIDMNotification(OpenidmAccountStatusNotificationHandler.java:620)} Pushing modification to queue for user: uid=test.sachin,dc=ihsmhosting,dc=com
    [22/Jan/2020:10:27:59 -0500] 43 trace thread={Worker Thread 15(59)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from 127.0.0.1:52928 to 127.0.0.1:1389 operation=ExtendedOperation(connID=70, o
    pID=1, oid=1.3.6.1.4.1.4203.1.11.1) } method={handleStatusNotification(OpenidmAccountStatusNotificationHandler.java:553)} Finished to process the notification to IDM for user: uid=test.sachin,dc=ihsmhosting,dc=com
    

    log looks okay to me but its not firing an event to its idm.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2020 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?