neogroupmanager/az
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added some further links to docs & cjwdev's GroupManager

Browse Source 
Signed-off-by: n@work <xy916229@git.do-not-reply@sys.wnd.sh>
This commit is contained in:
n@work 2025-02-14 19:23:17 +00:00
parent 91ea9dca5b
commit 307bad5b46
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -1,11 +1,11 @@
# neogroupmanager # neogroupmanager
## what? ## what?
neogroupmanager is a web-based application for managing on-premise Active Directory groups, similar to [Group Manager]() by [cjwdev](). neogroupmanager is a web-based application for managing on-premise Active Directory groups, similar to [Group Manager](http://www.cjwdev.co.uk/Software/GroupMan/Info.html) by [cjwdev](http://www.cjwdev.co.uk).
## how? ## how?
_pre-requisites: an Azure tenant, an [Azure Automation Account](https://learn.microsoft.com/azure/automation) with a Windows-based [hybrid worker](https://learn.microsoft.com/azure/automation/automation-hybrid-runbook-worker) connected_ _pre-requisites: an [Azure tenant](https://learn.microsoft.com/entra/identity-platform/quickstart-create-new-tenant), an [Azure Automation Account](https://learn.microsoft.com/azure/automation) with a Windows-based [hybrid worker](https://learn.microsoft.com/azure/automation/automation-hybrid-runbook-worker) connected_
_(via [PowerShell](https://learn.microsoft.com/powershell) or a UNIX equivelant)_ _(via [PowerShell](https://learn.microsoft.com/powershell) or a UNIX equivelant)_
1. `git clone https://git.wnd.sh/neogroupmanager/az neogroupmanager` 1. `git clone https://git.wnd.sh/neogroupmanager/az neogroupmanager`
2. `cd neogroupmanager` 2. `cd neogroupmanager`
@ -20,7 +20,7 @@ TODO: explain why cjwdev may not be good for a modern environment (cost, securit
## flowchart? ## flowchart?
TODO: a flowchart explaining the process end to end, however the basic idea is: TODO: a flowchart explaining the process end to end, however the basic idea is:
- azure static web app (SWA) hosts a frontend with access to perform c# code as api calls with the built-in function app (FA) - azure static web app (SWA) hosts a frontend with access to perform c# code as restful api calls with the built-in function app (FA)
- FA populate and query a table with a list of users who have access to the program, and the groups they manage, along with a queue of members to add/remove - FA populate and query a table with a list of users who have access to the program, and the groups they manage, along with a queue of members to add/remove
- azure automation account (AA) run a script every X minutes queries the table & queue for changes and acts on them, either updating the user's list of managed groups to be correct, or adding/removing users - azure automation account (AA) run a script every X minutes queries the table & queue for changes and acts on them, either updating the user's list of managed groups to be correct, or adding/removing users
- (optional) a logic app polls the queue/table for changes and triggers a webhook which causes the AA script to run, bypassing the need to run the AA script needlessly evert X minutes - (optional) a logic app polls the queue/table for changes and triggers a webhook which causes the AA script to run, bypassing the need to run the AA script needlessly evert X minutes