Expand my Community achievements bar.

SOLVED

Login protect on publisher

Avatar

Level 5

AEM 6.5

We have requirement that one part of the site (subset of pages under certain path) requires authentication (okta), how this can be accomplished?

Rest of the site should be accessible by anonymous users.

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 5

Hi @nbg62 ,

If your looking for some okta with SAML integration below is the reference for the same.

you can restrict the users to specific path by providing the path configuration and only that path will be under okta authentication.

https://wttech.blog/blog/2019/how-to-setup-aem-publish-saml-authentication-using-okta/#:~:text=Gener....

 

View solution in original post

4 Replies

Avatar

Community Advisor

Hi @nbg62 ,

Closed User Group (CUGs) is the answer. Closed User Group (CUGs) is a feature that is used to restrict the access to content to a select group of users on a published instance, need to log in to access the resource/content.

There are some official and unofficial sites to achieve the same. Kindly follow the steps as mentioned here.

Official

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

Un-Official: 

https://aemtutorials.com/close-user-groups-in-aem/

https://aemcorner.com/closed-user-groups-cugs/

Hope that helps!

Regards,

Santosh

Avatar

Correct answer by
Level 5

Hi @nbg62 ,

If your looking for some okta with SAML integration below is the reference for the same.

you can restrict the users to specific path by providing the path configuration and only that path will be under okta authentication.

https://wttech.blog/blog/2019/how-to-setup-aem-publish-saml-authentication-using-okta/#:~:text=Gener....

 

Avatar

Level 5

How I understand this will protect whole domain since main url redirects to example/demo (http://demo.example.com domain which is mapped to the /content/example/demo). Does this mean that http://demo.example.com/content/page1 is not protected ?


Is there a way to protect different routes, for example /content/page1/page12, content/page3... I couldn't understand where the protected paths are configured ?

 

Thanks