One of the recommendations from Keycloak, is to limit the access to the master realm, or use the system without it. However, before we do so, you must first ensure that your other realms has an administrator that can manage it. After which, we can safely disable the Master realm and manage our secondary realms using their respective administrative accounts. To do this, we should first login to the master

TL;DR : Using keycloak as an IDM or LDAP Domain Aggregator Download the APS Identity Sync Extension: https://github.com/alex4u2nv/aps-ais-authority-sync/releases/download/v1.0.0/aps-identity-sync-java-1.0.0-jar-with-dependencies.jar Configure APS to Integrate with Keycloak as in the example activiti-identity-service.properties Configure Keycloak to integrate with multiple LDAP domains via User Federation service. Authenticate into APS using users that were synchronized. If Keycloak authentication is enabled, then authenticate through keycloak If other authentication methods bounded to same user ids (email address) then use

Extending ACS 6 docker images After you have your ACS 6 local environment running, you’re probably thinking, this is nice, but I want to deploy my favorite amps, like JS console, Alfresco Governance Services (AGS), or even custom developed amps developed with Alfresco SDK.

Get ACS 6 EA on your local environment and start exploring new features, functionalities, and services.

By default Alfresco Content Services sets a default search limit, based on ACL checks to 1000 items. In order to search for more than 1000 items, you will need to do one of two things: However, before you make these changes, you should consider the use case behind your search requirement as a global change will allow users to run some very long accidental wildcard queries. If search is to

Loop through a result set, and execute an action on the objects. This example uses

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.

Install NPM https://www.npmjs.com/get-npm Start Alfresco Content Services, and Alfresco Process Services. Locally via SDK with default user/pass (admin:admin) #Fill in prompt to generate your project mvn archetype:generate -Dfilter=org.alfresco.maven.archetype: #After Project Generation, navigate into the project folder. chmod 755 run.sh ./run.sh Clone ADF project from github: git clone https://github.com/Alfresco/alfresco-ng2-components Navigate into the project’s demo-shell sub folder: cd alfresco-ng2-components/demo-shell If Alfresco Content Services and Alfresco Process Services is remote, then you must edit the

Issue: Default Administrators identified in Alfresco does not give the user Administrative privileges Troubleshooting: Check that there isn’t any space in your comma delimited list of names. Recommendations: If you are using LDAP sync to synchronize users, an LDAP admin group should be defined, and this group should be nested under the ALFRESCO_ADMINISTRATORS group.

This post allows the user to override the Alfresco Solr configurations in the Alfresco SDK 3.0 TL;DR Override Tomcat’s Solr context configuration to point to custom Solr4 config dir. Copy default Solr configurations into this directory. Override new configurations as needed. Override Solr Context Configurations First we will add a config element in our main pom.xml that carries the property of our Solr configurations. <solr.config.home>${basedir}/src/test/resources/solr4</solr.config.home> Next we will edit the

Why upgrade SDK 3.0? Support for RAD (Rapid Application Development) and TDD (Test Driven Development) via HotswapAgent and JRebel Simpler SDK layout Jar packaging by default Support for Alfresco version 4.2 to 5.2 Integration testing webscripts TL;DR Update your pom.xml Remove all SDK modules, except for your jar/amp project modules. Update your Integration tests. Add integration-tests project module, and copy src directory. Re-organize your Integration tests into the integration-tests project module, and rename to

IT departments today manage a massive amount of information, via a plethora of interconnected software components to provide businesses with the mission critical results that they need. To ensure the quality of these systems, IT departments are heavily invested in the testing, tuning and validation of these systems. The thought of validating these systems are already overwhelming, as a typical large-scale ECM system may consist of around 10 components, of