Hi @Syed_Shaik Yes it works for headless

Hi @Syed_Shaik , If your organization is capable of using third party connctor which is already developed to integrate aem with coveo then you can use Perficient handshake connector. This tool has lot of features to index the content in coveo from aem.If not in position to use tool then PFB1. From c...

We have mongo cluster of 2 author instances and the sling jobs distribution is random. Adobe says, in author cluster by default sling jobs will be distributed to all nodes in the cluster. But in our case sling jobs are randomly distributing i.e. sometimes jobA is getting distributed two author insta...

@laniweisbart were you able to get the SamlAuthenticationHandler.java ? Also please do follow below article to create a custom authentication handler.https://medium.com/@lars.auffarth/building-an-aem-custom-authentication-handler-for-okta-openid-connect-2d9d42c0161In above page at the end you can se...

@laniweisbart I saw you are referring to my post and possible solution is. If client has a login-token which is valid 12 hours from now and the client makes request after 12 hours then it is clearly a invalid token and the request will still be having login-token cookie but invalid one. In this case...

Hi @Developer_anon , Pls try below RewriteMap testMap txt:https://publish-p88805-e1164595.adobeaemcloud.com/bin/servlets/proxy/map.txtRewriteRule ^(.*)$ ${testMap:$1} [R=301,L] Create servlet which should give response as key value in new line Thanks,Ramesh

@deepankar2 If you are having 2 no of publishers with different domains and if you are expecting token to work without asking login then you need to use encapsulated token support. Please find below article for stateless authentication using crypto.https://experienceleague.adobe.com/en/docs/experien...

Hi @SDusane , could you please try below filter? Ensure you have name as VALUE instead of VALUEs filter: {deliveryGroup: {_expressions: [{value: $userGroups, _operator: CONTAINS}]}} Thanks,Ramesh.

@AvinashKu4 @kautuk_sahni I agree on this. This is the biggest problem with GraphQl. Even when you query for the fragment which is not present in system it always gives 200 response. Whatever you do it always gives 200 response. Graphql endpoint should handle the response codes properly.

@lavanya-merkle The most probable reason for workflow stuck in infinite execution is, there could be an exception somewhere in the code(in workflow or service/util referred in workflow). Particularly in workflows, if any exception occurs, then it will go to the try block and it will keep retrying th...