Unable to login with AEM username and password in AEMaaCS publish

Are you storing user credentials in publisher instance?

Thanks

204 No Content response indicates that the server processed the request successfully but has no content to send back. This is often used for actions that modify data without returning a specific payload. In this case, it suggests that the login attempt itself might have gone through, but the expected response (e.g., a redirect or user session information) is missing. Some potential causes and solutions to explore:

Authentication Mechanism:

• Check Configuration: Verify that the dispatcher configuration for /system/sling/login/j_security_check is correct. Pay attention to parameters like allowedPaths, allowedMethods, and sling:resourceType.
• Custom Authentication: If custom authentication is involved, ensure it's properly configured and error-free.
• Access Rights: Double-check that the user account has the necessary access rights to perform the login action.

Dispatcher Caching:

• Clear Cache: Invalidate the dispatcher cache for the relevant paths or enable debug mode to bypass caching during testing.
• Caching Rules: Review caching rules that might be interfering with login responses.

WKND Integration:

• WKND-Specific Issues: Explore potential WKND configuration or logic issues that might be causing the response to be empty.

Content Path:

• Double-check the content path in the error log (/content/wknd/language-masters/en/magazine.html). Ensure it exists and is configured correctly on the publish instance.

Cross-Origin Resource Sharing (CORS):

• If the WKND site and AEM instances reside on different domains, CORS must be properly configured on the dispatcher to allow login requests from the WKND origin.
• Double-check CORS rules in the dispatcher configuration (particularly the /0103 block) and adjust as needed.

HI @aanchal-sikka 
Do you see any error in the log?

Do you have sticky session if you are using multi-pub setup?

Seems like issue is due to logout/not having valid session.

There is an issue with aem login specifically in publish as soon as we done with the ui.config build in publish instance. This issue is with Adobe Experience Manager 2023.12.14697.20231215T125030Z-231200 AEM instance

The issue is with com.day.cq.rewriter.linkchecker.impl.LinkCheckerTransformerFactory.cfg.json configuration on line 

"linkcheckertransformer.stripHtmltExtension": true

@aanchal-sikka @kautuk_sahni 

@aanchal-sikka Were you able to fix this?