24th Dec, 2009

Alfresco Developer Guide source code update for 3.2 Enterprise

I’ve updated the source code that accompanies the Alfresco Developer Guide to be compatible with the recent 3.2 Enterprise release of Alfresco. You can get the link from my original post on the source code re-org, or download it directly.

Most of it hasn’t changed terribly much. The BootstrapAuthorityCreator class, which you don’t need unless you are playing with the AMP example in Appendix C, isn’t working yet due to changes in the AuthorityService with 3.2 Enterprise.

The biggest change is in the LDAP configuration (Chapter 9). Overall, setting up LDAP authentication and chaining has gotten much easier in 3.2 Enterprise. But the configuration is much different than in previous releases (See the Alfresco wiki pages on Subsystems and the Authentication Subsystem for more info).

I don’t have CAS SSO working with 3.2 Enterprise quite yet, so the authentication filter included in the Chapter 9 source code is commented out for now.

Responses

Hello,

My name is Ivone and I would like to ask you to join our affiliates program. Could you please give me an e-mail account where I can write to you?

Thank you very much,

Ivone

Hi Jeff, thank you for your big efforts about Alfresco and ECM in general. I’m using your book and web site as primary reference in my activity.

I’ll ask you if/when you can explain how we can set up Alfresco 3.2 to use CAS as login method – as you already told the chapter 9 is outdated ….

The main problem to follow the notes from the Alfresco’s wiki is their use of the Apache Web Server – Actually I integrated Liferay/Apache LDAP/JASIG CAS and I need to add Alfresco ECM and I don’t use a Web Server as front end.

Thank you in advance!

Ivano

Ivano,

I’m not sure why they changed the wiki page to use the Apache web server approach, although in production that’s a common way to set it up.

I believe that the last time I tested it, I got CAS to work with 3.2 Community following the same approach that’s in Chapter 9. However, when 3.2 Enterprise came out, I was definitely unable to get that working with the Chapter 9 approach, and noted that in the someco-server-extensions readme.txt in the 3.2 Enterprise-specific source code. I’m not saying it won’t work at all–it’s just that it won’t work as written in Chapter 9.

The 3.2 Enterprise release included what appears to be significant changes to the authentication implementation and I haven’t yet had time to dig in to them.

Jeff

Hi Jeff. If Alfresco is making all of these changes in the Enterprise system, are they abandoning the Community version? If not, how can they maintain two environments? Is it that well modularized so that they plug-in new features with minimal architectual changes overall?
Also, is it worth getting familiar with the community version if I plan to support the enterprise version in the future? Will my experience with the community version be easily applied to the enterprise? It seems that more and more features are going into the enterprise version and that overtime, they will be two similar but very different products with different paths of support.

Keith,

No, Alfresco is definitely not abandoning the Community version. The two are essentially (if not actually) the exact same code lines. The difference is that the Enterprise version adds a few features not available in Community. So, anything you’ve learned how to do in Community will apply to Enterprise. With that said, there can be a lag between a change that happens in Community and that change eventually making it into Enterprise, so sometimes there are slight variations in config, API, etc.

Unless there is a huge shift in Alfresco’s direction, I don’t think the changes going into Community will ever make the two flavors “similar but very different”.

Jeff

Leave a response

Your response:

Categories