DIspatcher for Author Instance | Community
Skip to main content
tc94524330
New Participant
January 28, 2016
Solved

DIspatcher for Author Instance

  • January 28, 2016
  • 17 replies
  • 5932 views

Hi,

I am trying to install dispatcher in front of author instance. When i try to open a page under content, i am getting prompt by login screen but i am enter the credentials admin admin, it still showing only login screen. 

Below are the couple of lines present in error log

 org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
 org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
 org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials
 GET /libs/granite/core/content/login.html HTTP/1.1] libs.granite.core.components.login.login$jsp j_reason param value 'unknown' cannot be mapped to a valid reason message: ignoring

 

Please reply to this question if anyone already configured dispatcher infront of author instances and if anyone has any steps to follow  for successful installation, that would be great.

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by leeasling

Browser cache and incognito mode have will not prevent the dispatcher from caching.  Are you sure you're deleting the dispatcher cache files before trying?

17 replies

tc94524330
New Participant
February 2, 2016

Hi,

I tried doing that. I tried in windows, linux and i tried with AEM 6.1, AEM 6. For all of these the result is the same. Could not login. This is happening only on local. 

I tried to configure dispatcher to DEV Author, it worked out but local is not good.

 

Thanks

Kunal_Gaba_
New Participant
February 1, 2016

Can you just test it by using a different domain other than localhost ? You can create a local domain in your machine hosts file and see if the issue still exists with the new domain. 

tc94524330
New Participant
January 31, 2016

Hi Opkar,

Thanks for taking your time to look at the question. It is working well if i access it directly.

As you requested, i am attaching logs for AEM and Apache also for reference. 

 

Thanks

Employee
January 30, 2016

Hi,

just to confirm it all works fine if you log out and try and access the url directly on author: you are prompted for password, it redirects and then page opens.

Can you also show the error.log and matching dispatcher log(you already posted this, but it would be good to have the error log for the same time) for when you try and access the page via dispatcher.

Regards,

Opkar

tc94524330
New Participant
January 29, 2016

Hi,

This is what exactly happening when i try to login. I get the login screen as usually when i try to access, as soon as i enter user id and password , it is generating a login token. After login token is getting generated, it is redirecting me to login screen again. I can relate to the events that are happening in browser and they are the same. 

Please find the attached log, it has logs from generating login token to redirecting it back to login screen.

 

Thanks

tc94524330
New Participant
January 29, 2016

Hi,

Yes, i do. I am deleting the dispatcher cache every time i try to login. 

 

Thanks

joerghoh
Employee
January 29, 2016

Ok, then the next thing is to turn the dispatcher to DEBUG loglevel and compare the responses you receive on the browser side with the responses the dispatcher gets from AEM.

leeaslingAccepted solution
New Participant
January 29, 2016

Browser cache and incognito mode have will not prevent the dispatcher from caching.  Are you sure you're deleting the dispatcher cache files before trying?

tc94524330
New Participant
January 29, 2016

Hi Jorg,

I delete browser cache, server cache every time i try to login. Even after that i open the links using Incognito window in chrome. There is no way cache can interfere.

 

Thanks

joerghoh
Employee
January 29, 2016

Hi,

it looks like that you cache all responses originating from /libs and /apps. Just in case, purge the complete dispatcher cache and try again.

kind regards,
Jörg