AEM Permission Management

About
APM (AEM Permission Management) is an AEM based tool focused on streamlining the permission configuration. It provides a rich UX console tailored for administrators. They can write human readable scripts that handle user/group creation/deletion and permissions application, both in bulk. Through it's flexible grammar, exposed API, and high extensibility it vastly improves permission-based implementations.

Features

• DSL (Domain Specific Language) that makes the script human readable.
• Auditability for all permission scheme changes.
• Support for glob regexp access, that's not available OOTB.
• Bulk changes for whole permission schemes.
• HTTP API access for better CI/CD implementations.
• Backend Java API for use of permission-based project features.

Compatibility
This page identifies the versions of Adobe Experience Manager with which a particular version of AEM Permission Management is compatible.
                    AEM 6.3    AEM 6.4    AEM 6.5

APM 5.x.x                                         x
APM 4.x.x         x                 x            x
APM 3.2.x                            x
APM 3.1.x                            x
APM 3.0.x         x 

Getting started
To start using APM an AEM in version at least 6.3 is required. The latest AEM packages are available here. Download both packages cq-actions-msg-replication and apm, and install them using CRX Package Manager.

How to use
Open APM dashboard http://localhost:4502/apm.html, and start using the tool. For more information visit user guide.

Documentation

• UI - quick tour for APM user's interface.
• Grammar - syntax of APM scripts, and description of main actions.
• Permissions - actions used for adding and revoking access to resources.
• Launchers - configuring auto execution of scripts.
• Backend API - executing scripts from backend services.
• Custom actions - implement your own action.

What's new?
APM 5.0.0

• Introduction of ANTLR 4.
• New way of registering actions (no regex, just friendly annotations).
• Improvements in UI (especially in script's editor and viewer).
• Introduction of new launchers (auto execution of scripts after package installation).
• Code separated in several modules (cleaner API).

Source: https://github.com/Cognifide/APM