Ismail Seyfi's Blog

Alfresco Share dashlet controllers can be used to call internal (Alfresco Repository) as well as external restful web services. In our environment our external restful web services are protected by CAS. In order to authenticate calls from Alfresco Share dashlets, CAS proxy authentication protocol is used. You can find much about CAS, its supported clients and protocols on their web site at http://www.jasig.org/cas. Cas ProxyAuthentication requires proxy tickets to be submitted with each service call. Therefore, proxy ticket must be generated and attached to each http call from an Alfresco Share dashlet. Here is snippet of a controller from one of our dashlets.  var hoursServiceUrl = remote.getEndpointURL("casProtectedService") + "/users/" + user.name + "/hours.json"; var proxyTicket = proxyTicketUtil.proxyTicket(hoursServiceUrl); var hoursUrl = hoursServiceUrl + "?ticket=" + proxyTicket; var hoursConnector = remote.connect(" casProte...

Alfresco is an enterprise content management solution. It can synchronize its user repository with Active Directory. When users are synchronized from Active Directory, Alfresco does not allow users to edit properties that are being synchronized with Active Directory. By default Alfresco synchronizes certain user attributes to Alfresco Person object properties. Some of these include users' first name and last name. If you want to include custom attributes you need to make sure that you set them up in the Alfresco configuration files.  There are different ways to modify and extend Alfresco. The safest way is to never touch any Alfresco properties in the WEB-INF/classes folder. They would get overridden when Alfresco is updated.  Alfresco recommends using Spring Beans to extend and override configuration. Here is a wiki page from Alfresco that talks about how to achieve this  http://wiki.alfresco.com/wiki/Alfresco_Subsystems#Spring_Bean...

I was trying to deploy Alfresco Content Management system into Geronimo. I downloaded the community war version and simply used the deploy script of Geronimo located in GERONIMO_HOME/bin/ to deploy the war file. As soon As I started Alfresco through Geronimo console, I ran into problems with Alfresco not being able to load MySQL Driver. Needless to say, MySQL database was chosen for this deployment. I ended up solving the problem by deploying MySQL driver into Geronimo. You can do this easily through the Geronimo console. On the left navigation of the console, there is a link called Common Libs below the Services folder. When you click on this, you will see an html form that lest you choose the jar file (in this case mysql-connector.jar). With in the form, you can give groupId, artificatId and version to the file. Once you submit the form, mysql connector will be deployed into Geronimo. What you need to do next is to create a geronimo-web.xml file and place it under WEB-INF directory o...