Highlighted

Not able to login in AEM Publish instance

Avatar

Avatar

hitesh_m

Avatar

hitesh_m

hitesh_m

02-03-2017

Hi, 

I am not able to login in AEM publish instance through web browser - 

<my_publish_instance_ip>:4503/crx/packmgr/index.jsp 

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. 

Replies

Highlighted

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

916

Correct Answer

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

916

Correct Answer

1.0K
Jörg_Hoh
Employee

02-03-2017

Hi,

Can you elaborate, what "not able to login" means? How have you tried that? What was the error message (was there any)?

cheers,
Jörg

Highlighted

Avatar

Avatar

hitesh_m

Avatar

hitesh_m

hitesh_m

02-03-2017

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 

  1. Request URL: <instancename>
    /crx/de/j_security_check
  2. Request Method:
    POST
  3. Status Code:
     
    403 Forbidden

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

Highlighted

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

02-03-2017

Looks like there is an issue with AEM authentication service. Have you successfully login to this instance in past? 

Highlighted

Avatar

Avatar

hitesh_m

Avatar

hitesh_m

hitesh_m

03-03-2017

Yes, I was always able to login.

Highlighted

Avatar

Avatar

leeasling

Avatar

leeasling

leeasling

03-03-2017

Check the referrer filter configuration and make sure the domain is allowed.

Highlighted

Avatar

Avatar

andrewj40704587

Avatar

andrewj40704587

andrewj40704587

07-03-2017

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. 

Highlighted

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

969

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

969

Correct Answer

1.1K
kautuk_sahni
Community Manager

14-03-2017

Did you try the solution provided by community experts?

~kautuk

Highlighted

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

08-08-2017

How did you solve the issue?

Highlighted

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

04-10-2017

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.