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 process stalls on the IdP - never redirecting back to AEM.
Interestingly, I can login to the AEM publish instance via the internal (/libs/granite/core/content/login.html) after switching it to JVM 11.
Here are some steps I've taken:
Initially, we tried deploying code compiled with Java 11 (but targeted to 1.8) to run on an AEM instance running under Java 1.8 - the new code did not start.
At some point we needed to delete a "repoinit" folder on author and publish to successfully start AEM (after deploying the Java 11 built code).
To run AEM under Java 11 - the following was added to sling.properties org.osgi.framework.bootdelegation:
jdk.internal.reflect,jdk.internal.reflect.*
I have since deleted repo.lock and cache.lock files, deleted the index folder, and deleted checkpoints, compacted tar files, and am rebuilding the indexes - still I cannot login, the indexes haven't been completely rebuilt yet.
I recall in the past Adobe had a password reset package the could be placed in the install folder, but also recall it stopped working at some point.
There don't look to be many things in the log files about this, on the SAML login attempt there is this:
15.04.2025 13:59:23.543 *INFO* [qtp1693777205-57] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
15.04.2025 13:59:23.553 *WARN* [qtp1693777205-57] org.apache.sling.auth.core.AuthUtil isRedirectValid: Redirect target must not be empty or null
15.04.2025 13:59:23.616 *INFO* [qtp1693777205-62] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
15.04.2025 13:59:23.626 *WARN* [qtp1693777205-62] org.apache.sling.auth.core.AuthUtil isRedirectValid: Redirect target must not be empty or null
Can someone recommend any other things we might try to recover access?
Thanks!
