Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/architecture/security.md
+12 -12
View File
@@ -2,7 +2,7 @@
title: "Security"
type: architecture
sources:
- areas/security/index.md (404 — compiled from cross-source knowledge)
- areas/security/index.md (404 - compiled from cross-source knowledge)
- areas/parameters.md
- areas/inventory_management/stations/roles.md
- modules cross-source knowledge
@@ -52,8 +52,8 @@ Password policies (minimum length, complexity, expiry) are configurable in syste
Operators can log in to RF terminals by scanning a personal QR Code instead of typing their credentials:
- The QR Code contains **anonymized data** — a third party who finds a lost QR Code cannot derive the operator's username or password from it
- **Each reprint invalidates the previous QR Code** — there is no revocation mechanism other than reprinting
- The QR Code contains **anonymized data** - a third party who finds a lost QR Code cannot derive the operator's username or password from it
- **Each reprint invalidates the previous QR Code** - there is no revocation mechanism other than reprinting
- QR Code login is **incompatible with SSO**: a user configured for SSO cannot use QR Code login
### SSO (Single Sign-On)
@@ -61,7 +61,7 @@ Operators can log in to RF terminals by scanning a personal QR Code instead of t
EasyWMS supports SSO using the **SAML V2.0 protocol**. No other SSO protocol is supported.
- SSO is available on both the **PC (SmartUI)** and **RF terminal** interfaces
- When SSO is enabled for a user account, EasyWMS will **not accept any other login method** for that user — standard username/password login is disabled
- When SSO is enabled for a user account, EasyWMS will **not accept any other login method** for that user - standard username/password login is disabled
- **SSO and QR Code are mutually exclusive**: enabling SSO on a user account prevents them from using QR Code login
- Configuration requires setting up the SAML identity provider (IDP) in EasyWMS system parameters and mapping EasyWMS roles to IDP groups
@@ -73,7 +73,7 @@ Authorization is evaluated at two levels:
Each Role grants access to specific navigation areas. A user who cannot access a menu item cannot reach the underlying Commands or Views from the UI.
### Command-Level Access
Individual AD Commands can be restricted to specific roles. This is enforced server-side — even if a user constructs an API call directly, the command execution checks the caller's role.
Individual AD Commands can be restricted to specific roles. This is enforced server-side - even if a user constructs an API call directly, the command execution checks the caller's role.
### Data Scope (Owner Isolation)
When the **Owner Extensions** module is active, data is isolated by owner:
@@ -161,10 +161,10 @@ The SCEM (Supply Chain Event Management) module allows subscribing to operationa
## Related
- [Overview](overview.md) — System architecture and deployment model
- [Application Dictionary](application-dictionary.md) — Role and permission configuration via AD
- [Transactions](../concepts/transactions.md) — Audit trail for all operations
- [Quality Control](../concepts/quality-control.md) — Stock lock system
- [Owner Extensions](../modules/owner-extensions.md) — Multi-owner data isolation
- [3PL Portal](../modules/3pl-portal.md) — External client access model
- [Supply Chain Event Management](../modules/supply-chain-event.md) — Notification subscriptions
- [Overview](overview.md) - System architecture and deployment model
- [Application Dictionary](application-dictionary.md) - Role and permission configuration via AD
- [Transactions](../concepts/transactions.md) - Audit trail for all operations
- [Quality Control](../concepts/quality-control.md) - Stock lock system
- [Owner Extensions](../modules/owner-extensions.md) - Multi-owner data isolation
- [3PL Portal](../modules/3pl-portal.md) - External client access model
- [Supply Chain Event Management](../modules/supply-chain-event.md) - Notification subscriptions