In CQ5 there is the login logout could be configured using a Closed User Group. Closed User Groups (CUGs) are used to limit access to specific pages that reside within a published internet site. Such pages require the assigned members to login and provide security credentials.
The logout using /libs/cq/core/content/login.logout.html always gets redirected to the geometrixx site http://localhost:4503/content/geometrixx-outdoors/en.html
By configuring the Default login page under the osgi configuration for com.day.cq.auth.impl.LoginSelectorHandler to be – /content/mysite/en/login
But still after logout the page goes to the geometrixx site.
IIRC, the redirect first goes to to / which then goes through the standard, somewhat complex handling of the root with multiple redirects:
1) / has a resource type of sling:redirect and redirects to /index.html
2) /index.html is handled by the RootMappingServlet [0] which has a configurable target
3) on author this target is set to /welcome (which is a sling:vanityPath for /libs/cq/core/content/welcome, the welcome page) [1]
4) on publish this target is set to /content.html [2]
5) /content is a sling:redirect with target of /geohome
6) /geohome is the sling:vanityPath of /content/geometrixx-outdoors
7) /content/geometrixx-outdoors has an rt of foundation/components/redirect which is like sling:redirect and finally redirects to /content/geometrixx-outdoors/en.html
Don’t ask me why this is so complex
But what you probably want to do is to adjust the sling:target of /content, which is essentially configuring the “default site”. If you use a vanity path or an explicit path here does not make a difference for the redirect.
[1] /libs/cq/core/config.author/com.day.cq.commons.servlets.RootMappingServlet
[2] /libs/cq/core/config.publish/com.day.cq.commons.servlets.RootMappingServlet
The default login page on the publish instance has to be configured to your sites login page, by default it points to geometrixx login page
Nhận xét
Đăng nhận xét