Chuyển đến nội dung chính

Login / Logout on a Publish instance and Closed User Group (CUG)

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

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...
Đăng nhận xét
Đọc thêm

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...
Đăng nhận xét
Đọc thêm

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...
Đăng nhận xét
Đọc thêm