since ‎08-03-2018
‎10-12-2019
yogeshVaidya
Level 2
Re: Are there any /bin/* urls that are at security risk in AEM? yogeshVaidya - Adobe Experience Manager
Thanks Joerg Hoh​I was asking the question for publish instance only. I will have to change my approach to resourcetype.
1215
Views
0
Likes
0
Answers
Re: Are there any /bin/* urls that are at security risk in AEM? yogeshVaidya - Adobe Experience Manager
Hi Jaydeep,I believe requests like ​ http://localhost:4502/bin/wcmcommand​ are used internally by AEM and thus I want to block those request on dispatcher as I don't the user to access these internal requests via public URL. I do have the rule that you have mentioned but. I want to block all URLs other than my own servlets via dispatcher as I want to expose my servlet only on public URL.I am looking for a standard approach/best practice. I had thought of serving all of my servlets via /bin/proje...
1085
Views
0
Likes
0
Answers
Re: Are there any /bin/* urls that are at security risk in AEM? yogeshVaidya - Adobe Experience Manager
Hi Anuj,though there are no nodes, I found that it http://localhost:4502/bin/querybuilder.json?path=/content_Path&type=cq:Page&p.limit=-1 this query builder's servlet was exposed over the dispatcher. I am looking for other servlets of AEM similar to query builder's servlet which are exposing data.
1085
Views
0
Likes
0
Answers
Are there any /bin/* urls that are at security risk in AEM? yogeshVaidya - Adobe Experience Manager
I am allowing all of the URLs starting with /bin in my dispatcher setup. I am also using various servlets with different extensions (.txt, .xml). I found out that my dispatcher is exposing querybuilder's .json URL. I have followed the dispatcher security checklist but it doesn't have the /bin/* URLs in the checklist. I am looking for a recommended approach for blocking /bin/* URLs.
2328
Views
2
Likes
7
Answers and Comments
Vanity URLs not working on AEM6.3 yogeshVaidya - Adobe Experience Manager
I am trying to implement vanity URLs in AEM 6.3. When I give a vanity URL to a page /content/project/en/abc as /content/project/en/xyz, mapping doesn't reflect on http://localhost:4502/system/console/jcrresolver and the page /content/project/en/xyz shows 404 error page. If I restart the AEM, Mapping and vanity URL works. Same thing happened if I re-update the vanity URL to /content/project/en/xyz1, the http://localhost:4502/system/console/jcrresolver show mapping to still /content/project/en/xyz...
908
Views
0
Likes
1
Answers and Comments
Re: Adobe Target integration with AEM yogeshVaidya - Adobe Experience Manager
We haven't specified sync or async attribute on script tags. So, i think sync is the default.
619
Views
0
Likes
0
Answers
Re: Adobe Target integration with AEM yogeshVaidya - Adobe Experience Manager
We are using Adobe launch. We have added added the dtm script using script tag in head.
614
Views
0
Likes
0
Answers
Adobe Target integration with AEM yogeshVaidya - Adobe Experience Manager
We have few buttons on our webpage. When "documentContentLoaded" event is fired, we are assigning event listener to the buttons. We have added target script in the head section and our client library is near the closure of body tag. Sometimes, target script is loading before our client and vice versa. When our client library is loaded before target script, event listeners get assigned to the buttons. Then target script loads which replaces HTML body with a new body. This deletes old buttons and ...
1298
Views
0
Likes
6
Answers and Comments
CSS minification in AEM yogeshVaidya - Adobe Experience Manager
I have used min:yui for CSS minification and min:gcc;compilationLevel=whitespace for js minification.js minification is working as expected(removing linebreaks and spaces) but CSS minification is only removing spaces. linebreaks are still present for CSS minification.I have found Minify JS CSS this thread but Don't know how to make changes for removing linebreaks.I am using AEM 6.3 and yui compressor version is 2.4.8
4512
Views
0
Likes
5
Replies
What should be the preferred approach to redirect old website's url. yogeshVaidya - Adobe Experience Manager
Our current website is not on AEM. We are replacing the current website with AEM based website. We have created all new pages. We don't want to redirect old urls to error page. We wish to permanently redirect old urls to similar pages. We have around 100 such urls. I am thinking of writing permanent redirect rules on apache web server. But as per my current logic I will have to write 100 redirection rules.Is this a good solution and Is there any other more feasible approach for the above require...
488
Views
1
Like
2
Answers and Comments
Re: Editable Templates - Access on /conf for anonymous user yogeshVaidya - Adobe Experience Manager
As explained by Arun, it is ok to have read access to /conf. Permission to /conf is required because you are probably adding client library through page design hence read permission to /conf(i.e. templates) is required. In cases where component level client libraries are used, permission to /conf is not required.
1518
Views
0
Likes
0
Answers
Re: template policies are not readable yogeshVaidya - Adobe Experience Manager
I was wishing to rewrite their names so that I'll be able to make package of policies related to certain templates.
607
Views
0
Likes
0
Answers
template policies are not readable yogeshVaidya - Adobe Experience Manager
All of my template policies are stored like "policy_1522132149527" even after giving readable policy Title and policy description. Whenever I am sharing package(containing editable templates) with anyone, it is difficult to identify policy of template so I have to create package without policies and then he(one with whom I have shared package) has to create policies in template. Is there any way to differentiate policies (right now, policies of all editable templates are stored inside /conf//set...
1187
Views
0
Likes
5
Answers and Comments
Re: Component specific ClientLibs? yogeshVaidya - Adobe Experience Manager
Though adding component level client library should be a perfect solution for your case, the only problem I am seeing is that the time required to load JS and CSS of that component.People prefer to load CSS at the head and JS just before end of body because they want to show static stylized content as soon as possible. If this(size of CSS and JS files) is not the problem then you can use component level client library.Are you using specific editable template(s) for those pages? if yes then will ...
1808
Views
0
Likes
0
Answers
Re: Workaround for vh units in aem 6.3 (touch ui editor) yogeshVaidya - Adobe Experience Manager
Hi dgordon86​,As of now, I have tried the same as you have stated(as mentioned in the question's description)I have used % units in edit mode and vh units otherwise.As you are saying, the editing v publishing experience isn't same.
846
Views
0
Likes
0
Answers
Workaround for vh units in aem 6.3 (touch ui editor) yogeshVaidya - Adobe Experience Manager
I need vh units for displaying images with height equal to view port. As per AEM 6.3 touch ui limitations, vh units aren't supported. Hence I have overwritten vh units with % unit for wcmmode = edit. But still vh and % units behave very differently on different devices and screen sizes. Hence I need something better than % units. Is there any other way to work with vh units?
1536
Views
3
Likes
5
Answers and Comments