- How to disable Link Checker or configure to mark links as valid in AEM
- Adobe Campaign: Queries against tsEvent take a long time
- How to reset the truststore in AEM
- Audience creation options
- How to look up Launch Darkly flags?
- “User name and password do not match” on login
- Adobe Campaign Standard: File Fails to upload if email entries contain “double”
- How to reset the admin password in AEM 6.3
- AEM redirects user back to http when accessed through SSL/TLS terminated Load Balancer | AEM
- Adobe Campaign: Is TLS 1.3 Supported?
- The Non-Apple SSO TV Provider Authentication Flow
- How to confirm if an MVPD is enabled for Apple SSO
- Change the minification engine for client libraries in AEM
- Adobe Campaign Standard: Can a collection within a collection be used within a JSON payload
- Error: Unable to parse expression ‘@registrationToken’
- How to debug client-side issues in the AEM Touch UI or Classic UI
- How to optimize Oak Lucene indexes to reduce indexing time
- Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x
- Marketing Channel Instances on Custom Links
- How to set the Oak login token session expiration
- Generating the missing renditions for AEM Assets
- SegmentNotFoundException and IllegalArgumentException
- How to delete the dispatcher cache without logging into to the Dispatcher server | AEM 6.x
- How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4
- ACC: Workflow best practices - Configuration and monitoring
- Adobe Campaign: BAS-010015 Cannot open file error causing “DeliveryParts” failure
- How to enable secure cookies in AEM
- “Response is committed” error during page load in AEM6.x
- Adobe Campaign Standard: API updates to profiles and services are not being reflected
- Audience Manager to Campaign
- Adobe Campaign Standard: Imported File Transfer activities cannot change external account
- How to block IP addresses at the Apache HTTP Server level?
- Check and analyze if JCR session leaks in your AEM instance
- SAML IDP POST to /saml_login URL returns 403 response
- Permission denied error from java.io.File.createTempFile
- Discover and Build Audiences
- AEM Thread Dump Analysis
- javax.jcr.NamespaceException: Unknown namespace prefix error in AEM
- How can I confirm if SSO is enabled or disabled for my Channel?
- Publishing of references broken on Touch UI
- DRM Error 3324 MachineTokenInvalid Sub Error Code = 111
- How to capture SSAI and Original Manifests Simultaneously
- Adobe Campaign Standard: Substitution of address for transactional messages
- Migrate users, groups, and ACLs between AEM instances
- How to clone a TarMK instance in AEM
- Adobe Primetime Authentication - Most frequently used terms
- How to reindex a synchronous AEM index | AEM, Oak
- How to run a datastore consistency check via oak-run
“User name and password do not match” on login
Description
When trying to log in to AEM, the error “User name and password do not match” is returned in a red box on the login screen.
When inspecting the network traffic via a browser debugger, a 403 error response is returned from an Ajax HTTP POST request to this URL:
/libs/granite/core/content/login.html/j_security_check
Environment
AEM 6.x
Cause
The user name or password could be incorrect or there could be an error from the authentication handler during login.
Resolution
To debug and fix this issue, follow the guide below:
Analysis
I. VALIDATE THE USER NAME, PASSWORD, AND THAT THE USER EXISTS:
If the issue only happens with one or a few users, then it could be that the wrong user names or passwords are being used or the users don’t exist in AEM.
CHECK THE PASSWORD:
- Use Chrome browser and open Developer Tools = Network tab in the browser, then, attempt to log in again.
- Select the POST request ending with j_security_check in the URL.
- In the lower-right panel of the Headers tab, scroll to the bottom.
- Validate that under Form Data, the password being sent in the j_password parameter is correct.
VALIDATE THAT THE USER EXISTS AND RESET THE PASSWORD:
- Log in as admin user.
- Go to the user administration screen.
- Verify that the users exist.
- Create the user if it doesn’t exist or reset the password if it does.
II. Analyze broken authentication handling
If none of the above solves the problem, then:
-
Log in to the AEM server’s OS.
-
Tail or view the error.log file.
-
View the updates to the log while attempting to log in to AEM.
-
If any errors or warnings are logged, then analyze those warnings. If nothing is logged, then enable a debug log with these settings:
Log Level: Debug
Log File: auth-debug.log
Loggers:
org.apache.sling.auth
com.adobe.granite.auth
com.day.crx.security.token
-
At this point, if you are unable to analyze the log messages, and find the root cause, then contact AEM Customer Support
Resources on adobe.com
Resources
Adobe Account
