Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Authentication mechanishim in publish

Avatar

Level 6

Experts,

I have to implement authentication mechanism same as how author instance works. For example, if any user request for any page http://localhost:4503/content/geometrixx/en.html then system should open the page http://localhost:4503/content/geometrixx/en/toolbar/account/login.html and only after successful login sling should redirect to required page. 

I looked into Login Selector Authentication Handler and Sling Authentication Service but it seems there is no configuration here. Could you please let me know your thoughts on how to proceed on this?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You can check for anonymous access.

Include this component in header. this component will redirect to login page if there is no session.

Thanks,

Maruthi

View solution in original post

3 Replies

Avatar

Level 1

You can achieve it using CUG. In the Advanced page properties of en.html; you can select the CUG as 'everyone'; and enter 'http://localhost:4503/content/geometrixx/en/toolbar/account/login.html ' in 'Login page' ; also check the 'enabled' check box. By this; for en.html; as well as its subpages; all users will be redirected to login.html. Please note that this will restrict all users; including the anonymous user as well to access the website.

Avatar

Level 6

Thank you for your reply Deepankar, How it will be possible without CUG and how same mechanism works in Author instance? 

Avatar

Correct answer by
Former Community Member

You can check for anonymous access.

Include this component in header. this component will redirect to login page if there is no session.

Thanks,

Maruthi

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----