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

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

A 5min POC using google sheets in Zeppelin. Testing how easy it would be to drop data into a spreadsheet, then analyze it using Zeppelin. First go into https://docs.google.com and create a new spreadsheet, which would be used for collecting your data. Alternatively, my copy of bank.csv, which is used in this example, can be cloned for yours. Next, you will want to create a shareable link for this spreadsheet,

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

Quick Steps Walkthrough This walk through is targeted for audiences who are new to Vault, or dev ops who just need an API to develop auto deployment scripts against. A production environment should be installed and operated by a Hashicorp Vault expert. Pull and Run Pull the docker image and run it in the foreground with exposed ports 8200 using the following command: docker pull vault docker run --cap-add=IPC_LOCK -p

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.

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

The Surf based Alfresco Share web application provides a highly customizable framework that allows you to override and customize the user interface via the share-config-custom.xml file. In this file, an evaluator element <config evaluator=”” condition=””> is used to target the elements for customization. These evaluators are managed by the SpringSurf XmlConfigService. This service is extended by the Alfresco web client framework to include the following default evaluators: string-compare defined by StringEvaluator