Azure AD can be used with AEM using saml integration: https://helpx.adobe.com/experience-manager/using/aem63_saml.html

I am looking for the service com.adobe.aem.dermis.odata.service.ODataConnector#executeRequest(), will have to see if this can be achieved by exposed classes in sdk.this class is exported by aem-dermis-odata-connector-2.0.54.jar. I am trying to avid the need to install the jar manually in maven repo ...

Hi Darren, I checked aemfd-client-sdk-6.3 jar, It does not seem to include the package com.adobe.aem.dermis.odata

We are working on a project that requires communication with ms dynamics crm from AEM. I see that AEM forms add-on already bundles an odata connector (aem-dermis-odata-connector-2.0.54) and would like to use it instead of adding a bunch of jars. But I cannot seem to find relevant maven dependency on...

Hi KhushwantSingh​, is there a forms reference implementation available in sightly/htl instead of jsps?

try this-RequestDispatcher dispatcher = request.getRequestDispatcher("/bin/wcm/contentfinder/asset/view.json/content/dam", opts);dispatcher.include(request, response);

try ${properties["carouselImages/item0/isActive"]}

I'd like to pass the handlebars expression using double curly braces '{{ foo }}' to the sightly variable, but I got errortoken recognition error at: '{'This is not possible, sightly is executed at server, the handlebars variable is available only on the client browser.

I assume you are obtaining the session by workflowSession.adaptTo(Session.class), if you create a session by logging in to the repository using spacialuser's credentials and use that session, replication will be attributed to that user.

ResourceResolver.getResource() return the resource at the exact path, resolve() methods would also look for sling mappings and take them into account before returning a resource.