Latest Posts

Archives [+]

Entries by Greg Klebus

    Posted by Greg Klebus MAR 04, 2011

    Comments 4

    file

    After releasing the CQ 5.4 WEM solution, we have also released a new version of CRX from Adobe, CRX 2.2. The relase includes the following main enhancements:

    • New Shared Nothing Clustering
    • Improved JCR 2 JQOM Query performance
    • Extended ACLs with wildcard support
    • Subversion integration using svn+ssh
    • Supports OSGi Service Platform Release 4.2

    There's also something special for developers:

    Download CRX, CRXDE & check the release notes for a more detailed summary of the release. Enjoy!

    Posted by Greg Klebus DEC 01, 2010

    Comments 2

    file

    We have just launched a package share community for Adobe CQ5 Higher Education CQ5 User Group in North America. This CQ5 customer group has been very active already before -- they formed the Higher Ed CQ5 User Group back in 2009. After the latest Ignite 2010 in Chicago Erin Yarbrough from the University of Oklahoma contacted me and asked to set up a Package Share community for their user group.

    And here it is - all the Higher Ed package share users from North America should see the new Higher Ed folder (in addition to their company's private folder). They all have read and write access to the new community folder. This way they can share content packages, projects, applications, packages, etc, in the group.

    file

    If you're interested in launching a community for your vertical or other customer / partner group (e.g., for a country or geography), let us know by writing to packageshare (at) adobe (dot) com!

    Thanks again, Erin!

    Posted by Greg Klebus NOV 01, 2010

    Add comment

    Our partner, Headstand Media, have published a community package on Package Share. It's called ImageSEO, and allows content authors on sites with many images to optimizes them for search engines, by providing an option of displaying fully-qualified image paths.

    file

    To check the component out, log in to Package Share from your CQ5 instance, navigate to Public » HeadstandMedia, and click Download on the ImageSEO package. Then install it in your local CQ5 instance, and use the component on your pages.

    Headstand Media have even provided a Knowledge Base article about the component.

    If you are interested in sharing your package(s) with the CRX Developer community, drop us a line at packageshare (at) adobe (dot) com.

    Posted by Greg Klebus OCT 31, 2010

    Comment 1

    During the Q&A session with Roy Fielding and product management at Ignite Chicago, nicely written-up by CMS Wire's Irina Guseva, I have received a couple of questions related to user/group/permission management in CQ5/CRX instances configured for LDAP authentication. While all the requested functionality is in the product, and the respective configuration and UI options are described in the LDAP documentation, I realized that we were missing a more generic overview of what the LDAP integration shipped with our products can actually do.

    I asked our documentation team to have a look at this, and they quickly provided an extended introduction and overview of LDAP integration. Please have a look at LDAP Authentication on docs.day.com, and leave comments there if you are still missing some information.

    Some of the questions hopefully answered by the new introduction include:

    • Q: (How) can I synchronize users/groups sourced from LDAP / Active directory with my CQ5 / CRX instance? A: Users and their groups (including configurable filtering and metadata matching) are automatically synchronized to your repository upon user's login. Additionally, you have the ability to manually synchronize user profiles (without forcing users to authenticate).
    • Q: How can I assign CMS permissions to the users coming from LDAP? A: We usually recommend assigning LDAP groups to CMS-managed groups (in CQ5), and then managing permissions for the CQ5 groups. LDAP groups usually reflect organizational structure, whereas CQ5 groups usually reflect CMS usage structure.
    • Q: Is it possible to do group matching from an AD group to the same group in CQ? A: As explained above, LDAP-sourced groups in CQ5 usually reflect the orgchart, and the CQ5-managed groups (like author, contributor, etc) reflect the CMS usage. You can have LDAP-sourced users belong to CQ5 CMS groups by assigning their LDAP groups to be members of the CQ5 groups.
    • Q: How can I assign permissions - the way you describe above - without forcing my users to log in to the system (what I call the "bootstraping problem"). A: use a few LDAP user names to manually synchronize their profiles. This will pull the necessary LDAP groups to CQ5, and will allow for assigning them to respective CQ5 "CMS" groups, which will give the LDAP users their CMS-side rights.

    Thanks to Hal Danziger, (@halwebguy) CTO at New York Media  for asking the questions. I also received a similar question from someone from University of Cincinnati, but could not find the person's name afterwards, sorry.

    Posted by Greg Klebus JUL 07, 2010

    Add comment

    I'm glad to announce that Ruben Reusser and Kyle Watson from Headwire.com, Inc. have contributed a code example package to the public CRX Developer Community area of Package Share. Thank you, Kyle and Ruben.

    cms-templatehandler package on Package Share

    We had a look at it and liked it very much - it's an example of a simple CMS with basic editing capabilities, also demonstrating templating capabilities and separation between content, design, and code. The sample templates are based on Joomla templates (converted to JSP). The application leverages Apache Sling framework and the JCR repository, and can be run, inspected, experimented with or further developed on CRX 2.1.

    To check it out, start your CRX 2.1 Developer Edition (or get one), head to Share on the welcome screen, login with your day.com account (or register). You will find the package in Public » CRX Developer Community » Headwire.com section, it's called cms-templatehandler. Download it to your local CRX, install, and open /site.html.

    Here's what you should see - a sample website, you can easily change templates, and edit content. Go to CRXDE Lite (Develop button on the welcome screen), and you will see the application under /apps/templatehandler and sample content under /site.

    file

    If you are interested in sharing your package(s) with the CRX Developer community, drop us a line at packageshare (at) day (dot) com.