How can we show only gated (Secure) Content for End User ? | Community
Skip to main content
Syed_Shaik
Syed_Shaik
Level 3
October 24, 2025
Solved

How can we show only gated (Secure) Content for End User ?

  • October 24, 2025
  • 2 replies
  • 278 views

Hi Team,

How can we display gated content (visible only after the user logs in) through the Dispatcher?

 

Example: I want to display a specific course to users after they log in to the website.

 

Thanks in advance,

 Syed Shaik.

 

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 Karishma_begumSh

HI @syed_shaik 

You cannot directly show gated content through cached Dispatcher pages — you must either:

Exclude gated paths from caching (auth required), or

Serve public shells + gated content via authenticated API calls

Use Authentication + Cache Segmentation

Protect gated content paths in Dispatcher configuration:
In your dispatcher.any (or .farm file), under /cache, deny caching for secure areas:

/cache { /rules { /0000 { /glob "*" /type "allow" } /0001 { /glob "/content/secure/*" /type "deny" } } }

Protect access using Apache authentication or SSO integration.

Example (in httpd.conf or vhost.conf):

<Location /content/secure> AuthType Basic AuthName "Restricted Area" AuthUserFile /etc/httpd/conf/.htpasswd Require valid-user </Location>

Once authenticated, the request passes through Dispatcher (uncached) to AEM, which delivers the page.

 

Hope this helpful:)

 

Regards,

Karishma.

 

 

 

2 replies

Karishma_begumSh
Karishma_begumShAccepted solution
Level 4
October 24, 2025

HI @syed_shaik 

You cannot directly show gated content through cached Dispatcher pages — you must either:

Exclude gated paths from caching (auth required), or

Serve public shells + gated content via authenticated API calls

Use Authentication + Cache Segmentation

Protect gated content paths in Dispatcher configuration:
In your dispatcher.any (or .farm file), under /cache, deny caching for secure areas:

/cache { /rules { /0000 { /glob "*" /type "allow" } /0001 { /glob "/content/secure/*" /type "deny" } } }

Protect access using Apache authentication or SSO integration.

Example (in httpd.conf or vhost.conf):

<Location /content/secure> AuthType Basic AuthName "Restricted Area" AuthUserFile /etc/httpd/conf/.htpasswd Require valid-user </Location>

Once authenticated, the request passes through Dispatcher (uncached) to AEM, which delivers the page.

 

Hope this helpful:)

 

Regards,

Karishma.

 

 

 

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    October 26, 2025

    You can use Permission Sensitive Caching so the dispatcher validates first if a file can be delivered to a requesting user. See https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/permissions-cache

      Terms & ConditionsAccessibility statement

      Loading footer...