# 🔐 SĂ©curitĂ© / Tokens — Quickstart (Fiche #23) ## TL;DR - **DEV/local**: `./run.sh` crĂ©e (si absent) `.env.local` avec des tokens et te donne un lien Dashboard. - **PROD/systemd**: `sudo ./server/install_prod_stack.sh` crĂ©e `/etc/rpa_vision_v3/rpa_vision_v3.env` **et gĂ©nĂšre automatiquement** les secrets/tokens si tu as laissĂ© `CHANGE_ME`. --- ## 1) DEV / Local (run.sh) Au premier lancement: ```bash ./run.sh ``` Le script va: - crĂ©er `.env.local` (permissions 600 implicites via umask) - charger les variables - t'afficher un lien: `http://localhost:5001/?token=` ### Appels API (exemples) ```bash # Read-only curl -H "Authorization: Bearer $RPA_TOKEN_READONLY" \ http://localhost:8000/api/traces/status # Admin curl -H "Authorization: Bearer $RPA_TOKEN_ADMIN" \ http://localhost:8000/admin/security/status ``` --- ## 2) PROD / systemd (installation) ```bash sudo ./server/install_prod_stack.sh ``` Le script: - copie `/etc/rpa_vision_v3/rpa_vision_v3.env` - gĂ©nĂšre automatiquement: - `ENCRYPTION_PASSWORD`, `SECRET_KEY` - `RPA_TOKEN_ADMIN`, `RPA_TOKEN_READONLY` - `AUTOHEAL_ADMIN_TOKEN` ### OĂč retrouver les tokens ```bash sudo grep -E '^RPA_TOKEN_(ADMIN|READONLY)=' /etc/rpa_vision_v3/rpa_vision_v3.env sudo grep -E '^AUTOHEAL_ADMIN_TOKEN=' /etc/rpa_vision_v3/rpa_vision_v3.env ``` --- ## 3) Rotation (si tu veux changer les tokens) ```bash sudo ./server/bootstrap_secrets_env.sh /etc/rpa_vision_v3/rpa_vision_v3.env sudo systemctl restart rpa-vision-v3-api rpa-vision-v3-dashboard rpa-vision-v3-worker ``` --- ## 4) Modes "safe" - `DEMO_SAFE=1` : bloque les endpoints "dangereux" (Ă©critures / admin), utile en dĂ©mo. - `RPA_KILL_SWITCH=1` : stop global (hard stop) tant que la variable est Ă  1.