Sorry coming late on this. Sharing some more pointer over here We invoke replication transport handler which connects with login auth module1 While doing test connection , current thread class loader SlingDynamic class loader which is able to interact login module 2 While replicating content , current thread classloader is ApplicationClassLoader which is not able to trace login module through transport handler. After replacing appclassoader with slingdyanmic classloader , works as expected. But ...

Hi , just like to re frame this issueWe have a login module(a.b.c.LoginModule) class specified in JAAS config. This login module gets invoked from class which implements Transport handler.(Generating token while replicating)Case 1When we do test connection or force retry for any content stuck in replication queue, the replication is triggered generating token from Login Module.LogsPOST /etc/replication/agents.author/agent1/jcr:content.queue.json HTTP/1.1] c.d.c.r.Agent.agent1.queue (ReplicationQ...

Thanks Aneeta,Nope we are not using any external Application Server.I don't think its related to any crypo related because I am not able to see any crypto related error.Infact it works after doing test connection as token is generated after that.I suspect something related to sequence of installation or any config may be I am missing which is causing this issue.

Thanks for immediate response.Yes, this behavior is happening in all lower environment.One more thing like to highlight , in AEM 6.0 we use tomcat server while in AEM 6.3 we used embedded jetty server.