I am not able to login in AEM publish instance through web browser -
But if I test the same from replication agent, it says "Test connection successful"
Also if I check it from CURL , like curl -u admin:admin http://localhost:4503/crx/packmgr/service.jsp?cmd=ls It works.
Can you please help me understand the issue.
Can you elaborate, what "not able to login" means? How have you tried that? What was the error message (was there any)?
I wanted to check some properties in CRXDE, hence I went to http://<my_INSTANCE>:4503/crx/de/index.jsp , I got the login window
I entered username and password (admin:admin) Workspace is crx.default
I got the error Provided username and password do not match.
However, the same instance works when I try curl -u admin:admin http://localhost:4503/crx/packmgr/service.jsp?cmd=ls
Error in the browser console is
Here are the logs in error.log
02.03.2017 16:52:22.188 *WARN* [qtp1345369604-2244] org.apache.sling.auth.core.impl.SlingAuthenticator handleSecurity: AuthenticationHandler did not block request; access denied
Hope this help
Looks like there is an issue with AEM authentication service. Have you successfully login to this instance in past?
Yes, I was always able to login.
Check the referrer filter configuration and make sure the domain is allowed.
Can you try restarting the instance? Have you checked the normal things like caps lock, pasting an extra space after the username or password, etc.
If you end up needing to reset the password you could try to package the admin user account from another instance (/home/users/whatever), then put that package in a /crx-quickstart/install folder on the local filesystem. The instance will pick it up and install it automatically.
Did you try the solution provided by community experts?
How did you solve the issue?
Another reason that could cause this issue is if there is a reindexing process running, such like the one suggested here: Performance tuning tips | 6.x that does affect /oak:index/nodetype. Running this will prevent pretty much any other operation in the publish instance, though it will be able to render content.