uProduce Dashboard Security and Security Headers – Quick Guide

Summary: This article covers the two quickest wins for securing XMPie uProduce: hardening the uProduce Dashboard (accounts, Global Settings and System Settings) and hardening HTTP security headers on the IIS frontend. For full infrastructure hardening, see the complete uProduce security KBA.

Audience: uProduce administrators and XMPie support personnel.

Important: Servers running XMPie software should be dedicated to XMPie only. XMPie is not responsible for issues caused by other installed applications (see Security Headers Hardening).

Application security (uProduce Dashboard)

Inside uProduce, enforce named accounts with least privilege, a strong password policy or domain authentication, short login sessions and hardened System Settings. Global Settings and System Settings both require the admin user.

Accounts and authentication

  • Protect the built-in admin. Change the default admin password at installation to a long, unique value stored in a password vault. Use it only for administration, never for daily production or integrations.

  • Named users only. Give every operator, designer and integration its own uProduce user. Never share credentials.

  • Domain / LDAP authentication (uProduce 13.2 and later). On domain-joined servers, create users with Windows domain or LDAP authentication so password complexity, expiry and lockout come from your domain controller. This applies across the Dashboard, uProduce APIs, uCreate Print connectivity and Circle. Use LDAPS (636) where possible.

  • Integration accounts. Create separate users for uStore, Circle and custom API integrations, scoped to the accounts they need, and rotate their passwords on a schedule.

  • MFA. uProduce does not enforce MFA itself; require it at the network layer (VPN or SSO gateway) for anyone reaching the Dashboard remotely.

Global Settings

Under Settings > Global Settings:

Setting

Recommended value

Why

Strong Password Settings (regex)

At least 12 characters with upper, lower, digit and symbol, e.g. ^(?=.*[a-z])(?=.*[A-Z])(?=.*\d)(?=.*[^\w\s]).{12,}$, plus a clear error message

Blocks weak passwords for locally authenticated users

Login token validity duration (minutes)

30–60 for interactive users

Logs out idle sessions automatically

Monitor Settings

Admin only

Hides server, service and database details from non-admins

System alert emails

Send to a monitored admin mailbox

Surfaces stopped services and low disk or database space

System Settings

System Settings (system admin only) hold the Dashboard's security switches (see System Settings). Change the first group from its default; confirm the rest keep their secure default after every upgrade.

Setting

Default

Recommended

Why

ForceSecureConnection

false

true

Requires HTTPS for the Dashboard

ForceQLingoLimitations

false

true, unless campaigns need QLingo extension functions or fetch

Blocks QLingo extension functions and fetch, which pulls data from the internet

ForceQLingoQueriesLimitations

false

true, unless plans need full query syntax

Blocks full-syntax queries that allow arbitrary SQL such as stored procedure calls

DisableInDesignScripting

false

true, if no workflow uses InDesign scripting

Removes scripting as a code-execution path on the server

AllowNonAdminShareWithOtherUsers

true

false, if sharing should be admin-controlled

Stops non-admins sharing accounts and reports with other users

SecureAssetURLs

true

true

Serves personalized assets through the authenticated REST API with signed URLs; turn off only if an integration cannot follow REST asset URLs. Signed URLs do not expire

RequireRequesterPasswordForSecuredActions

true

true

Re-prompts for the user's password on sensitive actions

AllowNonAdminManageAccountLevelEntities

false

false

Keeps delivery providers and post composition operations admin-managed

AllowNonAdminSetAllAccountsPermissions

false

false

Stops non-admins making their items available in all accounts

AllowNoneStrictImpersonationStrategy

false

false

Stops admins impersonating admins at the same level

Dashboard::ShowErrorDetails

false

false

Hides technical error details; enable only while troubleshooting

Dashboard::ShowVerifiedEmailsAdminOnly

true

true

Limits the verified email sender list to admins

ClaudeApiSettings, eSignSettings

JSON

Change only with XMPie Support

Hold API keys and client secrets; rotate them if exposed

Roles and permissions

  • Grant users only the uProduce accounts and campaigns they work on, with the lowest role that fits.

  • Assign delivery providers only to the uProduce accounts that need them, instead of the default of all accounts.

  • Review users and permissions quarterly; disable leavers on the day they leave.

API and integrations

  • Call uProduce APIs over HTTPS only, from allowlisted integration servers.

  • Store API credentials in a secrets vault or protected configuration, never in scripts or source control.

  • Treat all data and file names sent to uProduce from external systems as untrusted, and validate them in your integration code.

  • In Circle, connect only the subscriptions that need uProduce access; uninstalling the Circle Agent cuts all Circle-to-uProduce traffic (see XMPie Circle Security).

Security headers hardening

Apply XMPie's security-header configuration on the IIS frontend (proxy) server to reduce the risk of cross-site scripting, session hijacking and clickjacking (see Security Headers Hardening). The article applies to uProduce, uStore and XMPL.

Where to apply it. XMPie recommends a frontend (proxy) server in front of the backend. Apply the configuration on the frontend. If there is no frontend and the backend is exposed to the internet, apply it on the backend instead.

Procedure

  1. Back up the C:\inetpub\wwwroot folder.

  2. In C:\inetpub\wwwroot, delete:

    • the aspnet_client folder

    • iisstart.htm

    • iisstart.png

    • web.config

  3. Download XMPie's Configuration files, unzip them and place them in C:\inetpub\wwwroot.

  4. Restart the server.

After applying

  • Check the response headers of the Dashboard URL with your browser's developer tools or a header-scanning tool, and confirm the Dashboard, uCreate Print connectivity and integrations still work.

  • Re-check after IIS changes and uProduce upgrades, since the files in wwwroot may be replaced.

Checklist

☐Default admin password changed and vaulted

☐Named users only; separate integration accounts

☐Domain/LDAP authentication or strong-password regex configured

☐Login token validity set to 30–60 minutes

☐Monitoring visible to admins only; alert emails configured

☐ForceSecureConnection, QLingo limits and InDesign scripting set in System Settings

☐SecureAssetURLs and other secure defaults confirmed after upgrade

☐User and permission review completed this quarter

☐Security headers from Security Headers Hardening applied on the frontend (or exposed backend) and verified

 

The recommendations in this article are general guidance for self-hosted deployments and do not modify the terms of your XMPie Software License and Services Agreement.