Do CUGs work on Author instance? | Community
Skip to main content
Level 3
February 24, 2023
Solved

Do CUGs work on Author instance?

  • February 24, 2023
  • 1 reply
  • 555 views

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cug-doesn-t-work-on-restricting-permissions-for-a-specific-page/m-p/575270#M143789

I'm trying to work this out, but this doesn't work when I tried on my author instance.

https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/cug.html?lang=en 

I followed these steps pointed here.

 

Let me know if there are any other options to get this work.

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 lukasz-m

Hi @pixislinger,

You will not be able to test CUG on author instance. You will need publish instance for that. The entire process looks like this:

  • on author instance you are configuring/restricting specific pages/assets, this is described on documentation you have already refereed too https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/cug.html?lang=en
  • next you will have to publish group/user and restricted page/asset
  • last step will be to try to access gated content on publish - this will allow you to confirm that given resource requires user to sign in and it is not available for anonymous user (not signed in)

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
February 24, 2023

Hi @pixislinger,

You will not be able to test CUG on author instance. You will need publish instance for that. The entire process looks like this:

  • on author instance you are configuring/restricting specific pages/assets, this is described on documentation you have already refereed too https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/cug.html?lang=en
  • next you will have to publish group/user and restricted page/asset
  • last step will be to try to access gated content on publish - this will allow you to confirm that given resource requires user to sign in and it is not available for anonymous user (not signed in)