Testing CUG on Publisher instance

[nbg62]

hi,

it is AEMaCS, we're trying to test closed user groups on Publishing server but looking for a way to login to publishing instance using regular AEM login form as found on Authoring instance.

Thank you

[aanchal-sikka]

Hello @nbg62 

We cannot login to AEMaaCS publish instance.

For CUG, please create groups on Author and replicate to publish. Also, publish the folder on which CUG config was set up.

You can also try accessing content via Postman, by supplying the credentials. If the login is working fine for end-users on publish, you can try via test accounts.

But, we cannot login via browsers through AEM login screens

[nbg62]

Thank you, that's all setup but we don't have any 3rd party login IDP, so what's the solution to use CUG, what's the easiest way to login to Publishing instance ?

[aanchal-sikka]

@nbg62 

Without IDP integration, how are you planning to use CUG? Curious about the use-case.

Other choice is to create multiple technical accounts on Cloud manager, assign these users to groups and test CUG. 

This is blog is for using GraphQL with CUG: https://techrevel.blog/2023/06/07/securing-content-for-graphql-queries/

But, you can use majority of the steps, just replace GraphQL specific stuff, with pages/asset configs as needed

[nbg62]

>Without IDP integration, how are you planning to use CUG? Curious about the use-case.

I was hoping that cloud still supports "native" login as it was the case on 6.5.

[gangula2018]

Hello Aanchal-sikka, thanks for quick responses, and the blog link.

Here are some explanations -

IDP is not configured and ready to use, but AEM CUGs, Groups, Users and roles are all configured and published from Author to Publish.

- On Local dev environment (Like on any non-Cloud implementation) it is possible to test features around user access rights per paths on Publish instance by signing in through the out of the box page "libs/granite/core/content/login.html" - It is not possible to publish this page on Cloud version.

- By setting Authentication requirement as "Enabled", the default ootb login page throws 404 on publish instance, so this feature does not work on Cloud. Should it be disabled?

- In any case IDP is not part of Adobe offering, it is third party, and requires integration through SAML or OAuth... Can you clarify what does Adobe offer for Cloud to replace previously existing means of authenticating on publish instances on versions 6.5.x and lower, when third party IDP is not available?