On aem sites as cloud services i have my web content structured as following:
i have activated the proerty "enable authentication" and i have added a closed user group just for "it" section not for "en", by activating my my pages, user and group i am expecting on publish server that whenever a user tries to browse the "it" section aem must require authentication through the login page but the en section remains accessible to anonymous users. But in reality aem require authentication for "it" section which is fine but "en" section is no more accessible for anonymous user aem return 404.
i have already tried to use Apache Sling Authentication Service as alternative but the outcome remains same.
Thanks in advance!
no they are created manually through page creation procedure. if it can help i would like to share that they use static templates.
are en page accesible with login? can you check anonymous user and if that missing everyone group?
Can you clarify from where you are getting 404 Error for "en" page ( Publisher or Dispatcher ) if you are getting 404 error from dispatcher, tail your dispatcher log for the "en" page request and validate your resource resolver or etc mapping configuration for "en" content path in the publisher instance.
@Raja-kp i'm getting the 404 error for en page on publish. Could you please elaborate "validate your resource resolver or etc mapping configuration for "en" content path in the publisher instance."?
Thanks a lot.
Hi @Anmol_Bhardwaj please feel free to point out any mistake and share your suggestions
These look fine.
Can you try something like this in the "Adobe Granite Login Selector Authentication Handler":
And just keep the CUG in page properties for the it page. This should only redirect it page & sub-pages to the login page.
Have you deleted the existing changes which you have already done. Maybe one of them is causing this.
Also, the path should include my-site/it/*, to make sure it only picks up pages inside it.
I have used this way for CUG login multiple times(6.5.8,6.5.10,6.5.11), and it works.