Unable to Sign in to the local AEM 6.5 Publish Instance

Avatar

Avatar
Validate 1
Level 1
zameer_abbas
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
zameer_abbas
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
zameer_abbas
Level 1

12-10-2020

Hi,

 

I am not able to Sign in to AEM 6.5 Publish Instance. I cleared up the cache and cookies and still not able to login. 
I have signed in from the machine and with the same set up earlier as well. When I click on the login button I only get to see the 'Preference'. 
Please suggest what could be the issue here.

zameer_abbas_0-1602569805479.png

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 3
Level 2
dan_stelmakh
Level 2

Likes

3 likes

Total Posts

2 posts

Correct reply

1 solution
Top badges earned
Boost 3
Boost 1
Applaud 5
Affirm 1
View profile

Avatar
Boost 3
Level 2
dan_stelmakh
Level 2

Likes

3 likes

Total Posts

2 posts

Correct reply

1 solution
Top badges earned
Boost 3
Boost 1
Applaud 5
Affirm 1
View profile
dan_stelmakh
Level 2

13-10-2020

@zameer_abbas do you have this issue an a vanilla AEM 6.5 instance? I have the  similar one after Service Pack 6  installation. I haven't found the root cause yet. Meanwhile, you should be able to use /libs/granite/core/content/login.html as a workaround at the moment I guess.

Answers (6)

Answers (6)

Avatar

Avatar
Boost 5
Level 2
kerr
Level 2

Likes

13 likes

Total Posts

16 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 1
View profile

Avatar
Boost 5
Level 2
kerr
Level 2

Likes

13 likes

Total Posts

16 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 1
View profile
kerr
Level 2

13-10-2020

As part of a recent Service Pack the login/logout functionality has been removed from CRX/DE Lite.

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

13-10-2020

To debug and investigate the use case, please check the following:

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

 

 

Also, can you try restarting the instance? 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. 

 

Avatar

Avatar
Validate 1
MVP
Nirmal_Jose
MVP

Likes

119 likes

Total Posts

207 posts

Correct reply

58 solutions
Top badges earned
Validate 1
Establish
Coach
Contributor
Shape 1
View profile

Avatar
Validate 1
MVP
Nirmal_Jose
MVP

Likes

119 likes

Total Posts

207 posts

Correct reply

58 solutions
Top badges earned
Validate 1
Establish
Coach
Contributor
Shape 1
View profile
Nirmal_Jose
MVP

13-10-2020

Are you able to login into system console. If so,

1. Do you see any bundles not in active state. If so, please make them active

2. Open http://localhost:4502/system/console/configMgr/org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDa... and ensure rooth path is /crx/repository

Avatar

Avatar
Boost 250
MVP
Nikhil-Kumar
MVP

Likes

251 likes

Total Posts

262 posts

Correct reply

38 solutions
Top badges earned
Boost 250
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Boost 250
MVP
Nikhil-Kumar
MVP

Likes

251 likes

Total Posts

262 posts

Correct reply

38 solutions
Top badges earned
Boost 250
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile
Nikhil-Kumar
MVP

13-10-2020

@zameer_abbas  - Which version of AEM are you using ? 
Can you try restarting the server or try any other browser also check for any errors in console.

@vanegi @Arun_Patidar  Any suggestions on this ?

Avatar

Avatar
Establish
MVP
santhosh_kumark
MVP

Likes

99 likes

Total Posts

111 posts

Correct reply

38 solutions
Top badges earned
Establish
Validate 1
Give Back 3
Give Back
Boost 50
View profile

Avatar
Establish
MVP
santhosh_kumark
MVP

Likes

99 likes

Total Posts

111 posts

Correct reply

38 solutions
Top badges earned
Establish
Validate 1
Give Back 3
Give Back
Boost 50
View profile
santhosh_kumark
MVP

13-10-2020

Hi @zameer_abbas ,

 

1. Are you able to access http://localhost:4503 for publish which will redirect to http://localhost:4503/content/we-retail/us/en.html by default. If not there might be an issue with configuring publish instance setup.

2. Can you try running the same publish instance on other port number and check it(Ex:8080).

 

Links: https://helpx.adobe.com/in/experience-manager/6-3/sites/deploying/using/deploy.html

          http://aemconcepts.blogspot.com/2016/08/setting-up-author-and-publish-instance.html

 

Regards,

Santosh

Avatar

Avatar
Boost 5
Level 2
kerr
Level 2

Likes

13 likes

Total Posts

16 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 1
View profile

Avatar
Boost 5
Level 2
kerr
Level 2

Likes

13 likes

Total Posts

16 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 1
View profile
kerr
Level 2

16-02-2021