permission sensitive caching | Community
Skip to main content
varshsr
varshsr
New Participant
October 16, 2015
Solved

permission sensitive caching

  • October 16, 2015
  • 12 replies
  • 3871 views

I have a CUG protected page and implemented /auth_checker directly as below (sharing few lines of configuration)

but not able to see AuthChecker: initialized with URL 'configured_url'. in the dispatcher logs using apache 2.2 and dispatcher 4.1.7 in windows , please share any ideas

also share if dispatcher.any file with /auth_checker configured just to validate

/farms
  {
  /website 
    {  
    /auth_checker
      {
       /url "/bin/permissioncheck.html"

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 joerghoh

You should see a message on DEBUG level like this:

Authorization checker: initialized with URL '/bin/permissioncheck.html'

if you don't have this line, the permission check is not configured, thus PSC is not active.

12 replies

varshsr
varshsrAuthor
New Participant
October 23, 2015

Thanks David , Hoh . This is solved now . Issue was with a wrong httpd.conf getting loaded which in turn had loaded a wrong dispatcher.any

joerghoh
joerghohAccepted solution
Employee
October 22, 2015

You should see a message on DEBUG level like this:

Authorization checker: initialized with URL '/bin/permissioncheck.html'

if you don't have this line, the permission check is not configured, thus PSC is not active.

    varshsr
    varshsrAuthor
    New Participant
    October 22, 2015

    Any help / idea ?

    varshsr
    varshsrAuthor
    New Participant
    October 20, 2015

    Yes it is loading dispatcher.any but PSC is not effective

    D
    davidf46996755
    New Participant
    October 20, 2015

    Is Dispatcher definitely loading the correct dispatcher.any file?

    varshsr
    varshsrAuthor
    New Participant
    October 20, 2015

    Thanks , but it is not helping not seeing any log and still the CUG pages are not cached and log prints request contains authorization even when /allowAuthorized is "1"

    D
    davidf46996755
    New Participant
    October 19, 2015

    So sorry, I don't have a working configuration file.

    Are you sure that Dispatcher is loading the correct configuration file? If you intentionally break the configuration do you see errors in the Dispatcher log?

    For example, if you change "/auth_checker" to "/auth_checker_broken" or just "auth_checker_broken" (with no preceding slash), does Dispatcher complain?

    varshsr
    varshsrAuthor
    New Participant
    October 19, 2015

    please share a working dispatcher.any with /auth_checker configured to validate the configurations

    varshsr
    varshsrAuthor
    New Participant
    October 16, 2015

    i had checked configuration looks good and there is no error about auth_checker in the logs which makes me think if dispatcher is reading that section correctly ,is it possible to share any working dispatcher.any with auth_checker configured

    D
    davidf46996755
    New Participant
    October 16, 2015

    Ok sorry. I configured permission sensitive caching a while ago and I recall that I had to futz with the configuration to get it right. But I don't remember what exactly was the problem.

    If you put some garbage in there or misspell auth_checker does Dispatcher complain after startup about the broken configuration? Is Dispatcher definitely reading that section of the configuration?

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...