It looks like this issue was caused by the ConfigurationAdmin service.  We were referencing the ConfigurationAdmin in a service and it appears to be the culprit.@Reference private ConfigurationAdmin configurationAdmin; 

Just incase anyone else stubbles upon this in the future, I would like to add that this issue is caused by allowing the "authorization" header in the dispatcher to pass through to the publish server.  When the authorization header is passed, it will take priority over the login-token when the authen...

Thanks for responding @Vijayalakshmi_S Yes it's only happening on publishWe are including the config as part of our code repo and build

Hello community,I have been trying to troubleshoot a strange issue where the externalizer service configurations are being unbound - somewhat randomly.  This is occurring multiple times per day, and I haven't been able to attribute this issue to any particular event.  I am able to fix the issue by d...

Yes - this servlet would be invoked after the user has been logged in.

@Kiran_Vedantam Thanks for your reply.Correct me if I am wrong, but if a request is made to AEM and it contains a valid login-token, won't the authentication hander log the respective user into that AEM instance?  I can confirm that this behaviour is currently happening - if I add a valid login-toke...

@Asutosh_Jena_ Thanks for validating this for me.  I thought I was doing this right Something must be interfering with the request processing flow.  I'll keep looking and update the thread once I find the resolution.

Hi there community, I am looking to get the current logged in user from the SlingHttpServletRequest.  I am using a POST servlet that extends the SlingAllMethodsServlet. I can confirm that the login-token cookie is being sent with the request:String tokenCookie = TokenCookie.fromRequest(request).toSt...

It looks like this was caused by underscore is no longer being included in AEM the authoring JS.  After updating our custom authoring scripts the link button is working again. 

Hi all,After applying SP 6.4.8.4 the link button stopped working in our content fragments.Previously using the Multiline Text the link button worked as expected - once the SP update was applied the link button stopped working. Has anyone encountered this issue before? This JS error is thrown in the ...