We're hoping to run AEM under Java 11 but our SAML login and the internal (/libs/granite/core/content/login.html) login no longer work after updating the JVM (and still doesn't work when moving back to Java 1.8).The error I see for internal login is: User name and password do not match.For SAML, the...

@konstantyn_diachenko  And thank you so much for even more detailed info! 

@Jineet_Vora Thank you, this is very helpful info!

We currently run AEM under Java 1.8 but are developing a new codebase using an archetype requiring Java 11 to build the project. Our other site codebases are built (and run in AEM) using Java 1.8.Our new code base is built using Java 11 but I believe uses a config that targets Java 1.8, so as to be ...

We faced this issue recently and it was related to the system time being off. Syncing the system clock with NTP resolved the issue. Here's what we saw in the logs prior to updating the system clock:  ==> /apps/author/crx-quickstart/logs/error.log <== 07.04.2025 09:30:19.190 *INFO* [qtp1413716254-60]...

Thanks for the info, I had seen this too. I'm pretty sure we're not running AEM Dynamic Media Add-on. In this case I wonder if there are any other things that might break? In testing, I think we've been able to get a policy in place that allows us to start and stop the author and publish services su...

Does anyone know if AEM can be run under SELinux and if it is a supported configuration?  

@srinivas_chann1 This was helpful for me. I was attempting to optimize an XPATH query one of our page's components incorporates as a node / property. It was using:  //content/foo/en/bar/*[jcr:contains(@type, "*")] I found that * caused a traversal so hoped to OR all the valid values for "type" (and ...

Hi @Kamal_Kishor ;  I removed the listener java/class it didn't change the behavior, I tried the template/component in different paths of the site (after changing allowedPaths), and saw the same behavior.I asked Google Gemini: https://www.google.com/search?q=aem+property+changing+its+type+from+strin...

Hi @Kamal_Kishor -  Thank you for the suggestions.  I see the same behavior on a fresh 6.5 instance - w/o service pack and with SP 6.5.22.One interesting thing I see directly upon saving from page properties (to cause the issue) - in a log file: aemxyz.log:2025-02-20 13:28:10.242 DEBUG [com.xyz.aemx...