Monday, 28 September 2015

Customizing the Adobe Experience Manager Sidekick to improve the activate process

You can customize the AEM sidekick to add functionality tio meet your business requirements. For example, typically, once you activate an AEM page in author, in order to view it in publish, you typically copy its URL, paste it in new tab and change the host-name and port name to see the results. To simplify this use case, you can add a custom button to the AEM sidekick that performs these actions with 1 click.

The new sidekick button automatically give you the link to the page in publish instance once you activate it. That is, with a single click, you can see your current page in publish instance.




Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Friday, 18 September 2015

Creating an external OAK Login Module for Adobe Experience Manager

You can create a custom OAK Login Module for Adobe Experience Manager (AEM) that is called when a user logs into AEM from a 3rd party authentication system such as LDAP. To create a custom OAK Login Module, you use the javax.security.auth.spi.LoginModule interface. One use case for writing a custom OAK login module is to add custom application logic to a callback. That is, when a user logs in from LDAP, a callback is invoked.




 A custom OAK login module is implemented as an OSGi bundle. To read this development article, click  https://helpx.adobe.com/experience-manager/using/oak-login.html.


Note; For information about using LDAP with AEM 6.x, see Configuring Adobe Experience Manager 6 to use Apache Directory Service.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Wednesday, 16 September 2015

Configuring Adobe Experience Manager 6 to use Apache Directory Service

You can configure Adobe Experience Manager (AEM) 6 to  synchronize user account information from a third-party LDAP service. By configuring AEM to use a third-party LDAP service, you can authenticate LDAP users when logging into AEM. This article describes how to setup Apache Directory service (a popular open source LDAP service), create a new user, configure AEM 6 to use Apache Directory service, and finally login to AEM with the new user entered into Apache Directory service.



To configure AEM 6 to use LDAP, you configure these OSGi configuration settings:
  • Apache Jackrabbit Oak LDAP Identity Provider
  • Apache Jackrabbit Default Sync Handler
  • Apache Jackrabbit External Login Module
This AEM community article walks you through how to configure AEM 6 to authenticate Apache Directory service users. To read this development article, click https://helpx.adobe.com/experience-manager/using/configuring-aem6-apache-directory-service.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Friday, 11 September 2015

Using Jackrabbit UserManager APIs to create AEM Users and Groups

You can develop an Adobe Experience Manager (AEM) OSGi bundle that uses the Jackrabbit UserManager APIs to perform AEM user operations. This API provides access to both AEM users and groups and is located in the org.apache.jackrabbit.api.security.user Java package.

In this development article, a custom Sling Servlet is created that dynamically creates AEM users and groups using the UserManager API. For more information, see Interface UserManager.

AEM 5.6

The following illustration shows the AEM page that performs a POST operation to the AEM custom Sling Servlet that creates the user and group.


To read this development article, click https://helpx.adobe.com/experience-manager/using/jackrabbit-users.html.


AEM 6.1/6.2

The following illustration shows the AEM page that performs a POST operation to the AEM custom Sling Servlet that creates the user and group.


To read this development article, click https://helpx.adobe.com/experience-manager/using/using-jackrabbit-usermanager-apis-6.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

September Version of Ask the AEM Community Experts on Dispatcher

Join Scott Macdonald and J├Ârg Hoh @joerghoh (an Adobe employee and top AEM community member) for insight into using Dispatcher with Adobe Experience Manager.  By attending this session, you will gain a better understanding of Dispatcher as well as best practices for configuring, using and securing communication between Dispatcher and AEM.  We will also cover when it is appropriate to disable Dispatcher. This is your chance to ask questions on anything Dispatcher.

To watch this session, go to:

https://communities.adobeconnect.com/p8h87dumxgv/?launcher=false&fcsContent=true&pbMode=normal

Here is an older Dispatcher presentation that is very useful:

https://my.adobeconnect.com/_a295153/p7th2gf8k43/?launcher=false&fcsContent=true&pbMode=normal

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Thursday, 3 September 2015

Using Query Builder API from within an AEM 6.1 Sling Servlet

You can create an AEM application that searches the AEM JCR for assets and displays results to the end user. For example, you can use a custom Sling Servlet to search CQ pages under a specific repository node (for example, nodes under /content) and look for a specific search term. All content that satisfy the search criteria are included in the search results. To search the AEM repository, you use the Query Builder API from within a Sling Servlet. This API requires that you define search parameters, and an optional filter. After you execute the query, the results are stored in a result set. You can display the result set in an AEM web page.

When working with the Query Builder API, you can use a Java API or a Restful API. This development article uses the AEM Query Builder API within a custom Sling Servlet to perform searches.



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel