Deploying content and how credentials work
Deploying content and how credentials work
What it is
Your SpinetiX players sit on your LAN. The CreaRack cloud cannot reach them directly. The Local Agent — a small service running on a PC in the same network — does the device-facing work for you.
Publishing works pull-style. CreaRack gives each player a private content URL that contains a unique token. The Agent logs into the player once and configures its Scheduled Download to point at that URL. From then on, the player downloads its playlist from the cloud on its own, hourly — and the Agent forces an immediate refresh right after each publish. The player never needs a CreaRack login; the token in the URL is its key, and it is rate-limited server-side.
How to publish content to players
- Open Signage, go to the Content tab, and select your assets.
- Click Publish. Pick the target devices and playback settings, then confirm.
- If asked, provide SpinetiX credentials (see below).
- CreaRack builds a playlist, mints the tokenized content URL, and the Agent configures each player’s Scheduled Download and triggers an instant download.
- You get a toast per result: Published to N device(s) successfully or Published: X OK, Y failed.
To copy raw files into a player’s /content folder instead, select files and click Deploy Selected (N), choose the device, and confirm Deploy. The Agent uploads each file to the player over WebDAV.
Every action lands in the History tab, where View shows the detail and Restore reverts a player to its state before that operation. Publishing from the client portal is recorded there too. Administrators also see a warning at the top of that tab when a device keeps requesting a publish link that does not exist (because it was regenerated by a backup restore, revoked or expired): it lists the link, how many times and from which address it was requested, so you can reconfigure the screen with its current link from Setup.
How credentials are resolved
Players ask for an HTTP username and password. CreaRack resolves them in this order:
- Credential Store. If your organization has an HTTP credential saved in the Credential Store, CreaRack uses it automatically — no prompt.
- Manual prompt. Otherwise you get the SpinetiX Credentials (save in Config > Credentials to skip) dialog with Username and Password fields. What you type is used for this session only.
The security guarantee
- With a stored credential, the browser only sends the credential ID — never the password. The Local Agent receives that ID and fetches the username and password server-side, authenticated with its own token. The secret never passes through the browser.
- Manually typed credentials are ephemeral. They live in page memory only, are never written to disk or browser storage, and vanish when you reload.
- The player itself authenticates nothing against CreaRack: it downloads content via its token URL.
Troubleshooting
- Published: 0 OK, N failed or Deploy failed — the Local Agent is probably not running. The browser hands every device operation to the Agent at
127.0.0.1:5050; with no Agent, players are never touched. The cloud side is already updated, so start the Agent and publish again. - SpinetiX login failed — the player rejected the credentials. Check the HTTP credential in the Credential Store, or retype them in the prompt.
- Cannot reach SpinetiX — the Agent could not open the player’s IP on port 80. Verify the player is on, on the same LAN as the Agent, and its web interface answers.
- Asked for credentials every time — save an HTTP credential in the Credential Store to skip the prompt for good.
Related
- [[crearack—signage—contenido]]
- [[crearack—signage—pantallas]]
- [[crearack—signage—playlists]]
- [[crearack—settings—credential-store]]
- [[crearack—terminal—local-agent]]
- [[crearack—signage—troubleshooting]]
Véase también
- [[crearack—signage—contenido]]
- [[crearack—signage—pantallas]]
- [[crearack—signage—playlists]]
- [[crearack—settings—credential-store]]
- [[crearack—terminal—local-agent]]
- [[crearack—signage—troubleshooting]]