Some additional comments for others 1. Password complexity: "Apache Jackrabbit Oak AuthorizableActionProvider" (https://jackrabbit.apache.org/oak/docs/security/user/authorizableaction.html) (http://www.sgaemsolutions.com/2019/10/how-to-set-password-policy-for-aem-users.html?m=1) 2. for AEM Form on J...
@Mayank_Gandhi, We are looking here at template-type, not the actual template. We are just trying to understand where the configuration setting to allow or disallow the use the template-types from "/libs/settings/wcm/template-types". We do understand we can copy the template-type from libs to conf f...
Copy-past of the image text into plain text granite.js:259 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.structure.html:1 [DOM] Found 2 elements with non-un...
@Rakhi_Sukhadeve The issue is noticed in the browser when doing development. We normally use Chrome for development (Version 83.0.4103.97 (Official Build) (64-bit), this morning I tried Firefox and the issue does not occur in Firefox. I happen when you want to edit a template or adaptive form or si...
AEM 6.5.4 -I was looking for a guide/ sample on User password management. Found reference to 6.1 and even 5.x version, some no longer available, is there something more current? 1. configuring the user password policya. Max age allowed for a passwordb. How many charactersc. Password Complexity rules...
We did an additional test. In CRX/DE we copied one of the template types from "/libs/settings/wcm/template-types" to "/conf/<folder>/settings/wcm/template-types". Now this template is appearing a a available template.
AEM 6.5.4. When we want to create new templates, the system needs you to select a template-type. We notice that for some folders in /conf/<folder> the template types showing up include the templates for adaptive forms that are taken from "/libs/settings/wcm/template-types". On the other hand for oth...
AEM Forms on OSGI 6.5.4. We are tracing where the the following meta tag originate from:<meta name="viewport" content="user-scalable=no"> /conf/<folder>/settings/wcm/templates/<name> type "cq:Template" with jcr:content "cq:templateType" = "/libs/settings/wcm/template-types/afpage"under structure/j...
Recently we see these errors coming up over and over again in Author when designer templates, forms, ... Any clue where this is coming from. core.js is not a script file we can read easily.