AEM Hide Images in Asset finder for NDA/Secret projects


 In order to hide images from asset finder we need to overwrite below file to /apps

/libs/cq/gui/components/authoring/assetfinder/asset/asset.jsp

We can create a folder and any images available under that folder can be ignored while displaying in asset finder tab using below code

boolean showimage = true;

if(imgSrc.indexOf("/internal_image/") > -1) {

    showimage = false;
}
if(request.getQueryString().indexOf("internal_image") > -1 && xssAPI.encodeForHTMLAttr(imgSrc).indexOf("/internal_image/") > -1) {

    showimage = true;
}
if(showimage) {
%>
 Leave code as is provided by Adobe
<%
}
%>


Code Explanation:

 Below code will remove the image if it is present under internal_image folder

if(imgSrc.indexOf("/internal_image/") > -1) {

    showimage = false;
}

In order to display the images for using in components, authors who are aware of folder path can search in asset finder, below code will make the image available if author is searching with folder name

if(request.getQueryString().indexOf("internal_image") > -1 && xssAPI.encodeForHTMLAttr(imgSrc).indexOf("/internal_image/") > -1) {

    showimage = true;
}

With above code we can create multiple internal_image folder (or any custom name) in any folder and add the images which should not be displayed on asset finder.

We can also create a configuration to list down the folders instead of hardcoding the value. 

Comments

Post a Comment

Popular posts from this blog

AEM integration with Akamai Fast Purge API for Single/multiple urls

Image
In AEM we can clear dispatcher cache on page activation by adding dispatcher flush agent but if we have Akamai on top of dispatcher as CDN then we need to manually clear Akamai Cache by going to akamai console. Akamai provides fast purge API and using that we can clear page cache using single URL, CPCode, multiple urls etc We can integrate Akamai Fast Purge API with replication agent so that for every page activation akamai cache gets cleared. To integrate with Akamai Fast Purge we need below details (Contact Akamai for details related to your account) 1) Access Token 2) Client Secret 3) Client Token 4) Akamai Host API End Points ( https://developer.akamai.com/api/core_features/fast_purge/v3.html ) Once above details are gathered you can refer below code for multiple urls cache clear Create a map with array list of urls  Map<String, List<String>> akamaiRequestMap = Maps.newHashMap(); ArrayList<String> arrayList = new ArrayList<>(); arrayList.add("Ad
Read more

AEM Results count using query builder

Image
 Using below query builder we can get the list of pages/assets count returned in json format Page Count: http://localhost:4502/bin/querybuilder.json?path=/content/we-retail&property=jcr:primaryType&property.1_value=cq:Page&p.limit=-1 Assets Count: http://localhost:4502/bin/querybuilder.json?path=/content/dam&property=jcr:mimeType&property.1_value=image/gif&property.1_value=image/png&property.2_value=image/jpeg&property.3_value=image/svg+xml&p.limit=-1
Read more

AEM - Rollout a page programmatically and update references

 Out of the box RolloutManager provides below 3 methods by using that we can rollout the page programmatically. 1) void rollout(RolloutParams params) throws WCMException; 2) void rollout(ResourceResolver resolver, LiveRelationship relation, boolean reset) throws WCMException; 3) void rollout(ResourceResolver resolver, LiveRelationship relation, boolean reset, boolean autoSave) throws WCMException; But when using 2nd and 3rd method we are able to rollout the page but the link references are not getting updated to the corresponding locale. This is because we are not providing the rollout trigger in 2nd and 3rd methods, so referenceUpdate is not getting triggered.  In order to update the link references in the rollout page we need to use 1st method and pass/set the required details in RolloutParams class. Below is example code for setting the RolloutParams                                              RolloutParams rolloutParams = new RolloutParams();                                      
Read more