Most development projects rely on protected, external resources, such as databases, or rest services; and many times, for the sake of simplified testing, we add those credentials to our configuration files, which, if accidentally leaks to the wrong person, can become a painful and expensive issue. In this article, I will demonstrate how to avoid these issues in a Java, Maven development environment. Password leaks can be avoided by simply

Audit Replication of Alfresco Content Services (ACS) to Elastic Search using Spring Boot and Apache Camel. This project uses a Pull/Push integration model, where the ACS audit stream is pulled from the Rest API, and pushed over to Elastic Search. Once audit data is in Elastic Search, the Kibana UI can plug in to generate dashboards and charts based on audit actions inside of Alfresco Content Services.