Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Integrate reviewed terminal token-file preservation coverage

pulse-triage[bot]297f933d45d6
diff --cc docs/UNIFIED_AGENT.md
index 645b461fcd,fe6472ac9e..b3b991e433
--- a/docs/UNIFIED_AGENT.md
+++ b/docs/UNIFIED_AGENT.md
@@@ -1206,14 -1196,12 +1206,22 @@@ Quotes or a prefix can cause rejection
right scopes. A rejected credential can leave that record showing `Never`;
this does not identify the cause of a particular installation's failure.
+**Bare does not mean intact.** For a token from the current **Infrastructure →
+Install on a host** generator, privately check the 64-character lowercase
+hexadecimal shape described in [private-file installation](#private-file-installation-linux-macos-and-nas).
++
+ A matching token hint confirms only the visible ends, not the whole token.
+The inventory's **Hint** shows only the first six and last four characters:
- duplicated or changed middle characters can leave both ends matching. Even an
- intact shape and matching hint do not prove full equality, the intended Pulse
- instance or accepted reporting. Do not apply this shape check to other token
- families or rotate a working credential because it looks different.
++duplicated or changed middle characters can leave both ends matching.
+ Pulse authenticates the whole token: duplicated or missing characters in the
+ middle can still cause rejection. Finding such a difference does not establish
-which step introduced the error. Legacy token formats remain supported;
-do not replace a token merely because its length or format differs from a
-newly generated one.
++which step introduced the error. Even an intact shape and matching hint
++do not prove full equality, the intended Pulse instance or accepted reporting.
++
++Legacy token formats remain supported; do not replace a token merely because
++its length or format differs from a newly generated one. Do not apply this
++shape check to other token families or rotate a working credential because it
++looks different.
Use how the file was saved or an existing private observation. If you cannot
safely tell, say **unknown**. If asked, report only **bare**, **quoted**,
diff --cc frontend-modern/public/docs/UNIFIED_AGENT.md
index 645b461fcd,fe6472ac9e..b3b991e433
--- a/frontend-modern/public/docs/UNIFIED_AGENT.md
+++ b/frontend-modern/public/docs/UNIFIED_AGENT.md
@@@ -1206,14 -1196,12 +1206,22 @@@ Quotes or a prefix can cause rejection
right scopes. A rejected credential can leave that record showing `Never`;
this does not identify the cause of a particular installation's failure.
+**Bare does not mean intact.** For a token from the current **Infrastructure →
+Install on a host** generator, privately check the 64-character lowercase
+hexadecimal shape described in [private-file installation](#private-file-installation-linux-macos-and-nas).
++
+ A matching token hint confirms only the visible ends, not the whole token.
+The inventory's **Hint** shows only the first six and last four characters:
- duplicated or changed middle characters can leave both ends matching. Even an
- intact shape and matching hint do not prove full equality, the intended Pulse
- instance or accepted reporting. Do not apply this shape check to other token
- families or rotate a working credential because it looks different.
++duplicated or changed middle characters can leave both ends matching.
+ Pulse authenticates the whole token: duplicated or missing characters in the
+ middle can still cause rejection. Finding such a difference does not establish
-which step introduced the error. Legacy token formats remain supported;
-do not replace a token merely because its length or format differs from a
-newly generated one.
++which step introduced the error. Even an intact shape and matching hint
++do not prove full equality, the intended Pulse instance or accepted reporting.
++
++Legacy token formats remain supported; do not replace a token merely because
++its length or format differs from a newly generated one. Do not apply this
++shape check to other token families or rotate a working credential because it
++looks different.
Use how the file was saved or an existing private observation. If you cannot
safely tell, say **unknown**. If asked, report only **bare**, **quoted**,