Configure dispatcher for permission-sensitive caching - Using an external service | Community
Skip to main content
S
StevenRymenans
Level 2
January 19, 2016
Solved

Configure dispatcher for permission-sensitive caching - Using an external service

  • January 19, 2016
  • 1 reply
  • 1174 views

Hi,

I followed the documentation on https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html to configure the auth_checker to check the permissions. When I check the dispatcher log I see that the authentication checker is used, but the url is always called on the publish instance. Is it possible to use an external service to validate the permissions?

I want to use an external service, because AEM doesn't contain the users session information.

Kind regards

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 Peter_Puzanovs

Hi Steven,

 

OOTB functionality does not allow you to point to a custom authentication endpoint. As far as I know.

Ideally, you should handle authentication in publisher boxes. Example impl [1]

This surely, depends on load you are expecting on your servers. Given too big load it would be highly complicated to validate all requests on publishers.

For this use case, you would put a proxy server in between(Publish - Proxy - Dispatcher). Proxy would intercept authentication path requests and forward them to the desired authentication endpoint, which would in return validate user/path and return desired (success|fail) opcode back to the dispatcher.

 

[1] https://helpx.adobe.com/experience-manager/kb/PSCachingDelivery.html

Thanks,

Peter

1 reply

Peter_Puzanovs
Community Advisor
Peter_PuzanovsCommunity AdvisorAccepted solution
Community Advisor
January 19, 2016

Hi Steven,

 

OOTB functionality does not allow you to point to a custom authentication endpoint. As far as I know.

Ideally, you should handle authentication in publisher boxes. Example impl [1]

This surely, depends on load you are expecting on your servers. Given too big load it would be highly complicated to validate all requests on publishers.

For this use case, you would put a proxy server in between(Publish - Proxy - Dispatcher). Proxy would intercept authentication path requests and forward them to the desired authentication endpoint, which would in return validate user/path and return desired (success|fail) opcode back to the dispatcher.

 

[1] https://helpx.adobe.com/experience-manager/kb/PSCachingDelivery.html

Thanks,

Peter

Terms & ConditionsAccessibility statement

Loading footer...