IT Sistemi – SCOM Management Pack for Alfresco on Unix is designed to work with Alfresco Enterprise installations that are deployed on Unix-derived platforms which include popular Linux distributions like Red Hat Enterprise Linux, Novell SUSE, or CentOS. Management pack can be configured to monitor remote Alfresco deployments so this management pack can also be used to monitor Alfresco installations deployed on Microsoft Windows operating system.
Management pack is available for free to all interested customers for a limited time period. Beta version of this management pack expires on October 1st and it will stop functioning on that date. Please note that we left out some functionality that is not working at the moment or we otherwise found it not ready for the public distribution at the moment. To get all the management pack features you will need to monitor Alfresco Enterprise version due to Alfresco Community version limitations.
You can download the IT Sistemi – SCOM Management Pack for Alfresco on Unix by filling out the request form on the IT Sistemi website. Installation instructions are included with the download. Continue reading
My last article on Alfresco integration with Active Directory brought up a lot of interest and what’s the most important positive feedback. That article is based on Alfresco Community version 3.2r2 so if you are using that version please continue reading that article.
This article will cover the latest community release 3.3g. On one hand I’m going to leave out most of the explanations that you can find in the original article and I’ll focus on getting things done in a focused article. You can also refer to the chapter 6 of the Professional Alfresco: Practical Solutions for Enterprise Content Management (Wrox Programmer to Programmer) [amazon.com] book or to the chapter 4 of the Alfresco 3 Enterprise Content Management Implementation [amazon.com] book.
Still, plan is to provide newcomers clear guides what has to be changed or to be more precise what is domain specific so I’ll make sure to insert “(domain specific property)” in code comments. Also, since version 3.3g supports document editing via Google Docs I’ll cover configuration of Google Docs integration as well. Again, I’ll repeat myself, for detailed explanation how stuff works refer to the original article as concept is the same. So let’s begin…
After the first article about Alfresco’s integration with Active Directory has spurred a lot of interest I’ve decided to write a follow up article that shows how to use Kerberos for authentication. I’ll divide the article in three main parts:
- Description of Kerberos authentication process
- Setting up requirements for Kerberos implementation
- Alfresco configuration parameters for Kerberos
As some of you might have seen Alfresco team have published a roadmap for the year 2010. I must say I’m very pleased with the latest community version 3.2r2 (actually, couple more SVN releases than the official 17458 but lets not be picky). In my opinion, it is finally what was 3.0 “Stable” supposed to be and I’m not counting the DoD module here but the overall stability of the product.
My wishes for community edition in 2010:
- content store selector available in enterprise edition only
- better support for Windows 7
- fine-tuning of UI controls in Share as some are really not available where they should be, hint: Edit Online on document details page
- content modeling in GUI not just in XMLs
- ability to chain SSO authentication with something non-SSO e.g. NTLM SSO + ldap if it is even technically possible
- faster merging of bug-fixes from enterprise branch
- better support from Alfresco team in forums though I must say they’ve been very helpful in last 6-9 months
- publishing critical patches for last stable community release and not just telling people to “it’s in HEAD”
- abandon policy to have certain functionality in enterprise edition only as legally possible
+ of course, everything they have in their published roadmap 😉
If you are the guy/girl responsible for implementing permissions model for your business case you might find yourself in trouble. Let us imagine a scenario where business case states that certain users should be able to create new content but not be able to delete anything. That’s the easy one, you’ll likely say, and assign Contributor role to those users.
Lets check Contributor role definition from the Alfresco wiki:
Includes the Consumer permission group and adds AddChildren and CheckOut.
They will, by default own anything they create and have the ROLE_OWNER authority.
Hm, ROLE_OWNER looks suspicious:
“FullControl” granted to “ROLE_OWNER”
The owner (as defined by the ownable aspect, or, if the aspect is not present the node creator) is allowed all rights. This interacts with contributor for cm:content. They only need the right to create content in the default set up; all other rights come from the fact that they own the nodes they create.
To sum up the above, users that are just contributors can delete everything they create and you likely don’t want that.
So what can we do to fix this. There are two options and both have certain drawbacks. Continue reading
One of the main features of the Alfresco ECM System is the ability to integrate user authentication and synchronization with Microsoft Active Directory.
Unfortunately, integration is not trivial and it is error prone. While I’ll provide explanations how stuff works you can also have a look at the chapter 6 of the Professional Alfresco: Practical Solutions for Enterprise Content Management (Wrox Programmer to Programmer) [amazon.com] book or to the chapter 4 of the Alfresco 3 Enterprise Content Management Implementation [amazon.com] book.
In this guide I’ll show you how to achieve full integration with Active Directory which includes Alfresco Explorer and Alfresco Share SSO, CIFS SSO, and Active Directory (LDAP) users and groups synchronization. Continue reading