A new platform update introduces a improvement in the way Web Sites are configured and initialized in our platform. This new functionality simplifies setup, enhances security flexibility, and reduces unnecessary license usage — especially for system-level sessions.
What’s New?
When a Web Site (including API sites) starts or re-initializes, it typically needs to create a background service session for internal operations. Previously, that system session consumed a license, even though no real user was involved.
With our latest update, that’s no longer the case.
Key Functional Enhancements
-
Web Sites can now run under the
SYSTEMuser — a predefined technical user for internal use. -
The
Trusted Applicationfield can now be left empty — and this is now the recommended default. -
The system session used for managing the site will NOT consume a license.
Why It Matters
This enhancement significantly improves the clarity and efficiency of site configuration:
-
It eliminates the need to manually define and assign trusted applications for technical purposes.
-
It ensures that system sessions — those used solely to support the web site's background functionality — no longer take up valuable licenses.
-
User sessions still require a license, as before. This change affects only the platform's own internal processes.
Recommended Configuration
Going forward, when creating or editing a Web Site:
-
Simply leave the
Trusted Applicationfield empty. -
This will automatically enable the new behavior.
-
Only in rare cases — where you need to restrict the site's internal permissions — should you define a specific Trusted Application.
In Summary
-
More control, less configuration.
-
No license consumed for system sessions.
-
Clean, recommended defaults that just work.
This change improves both security and scalability — allowing you to run more sites, more efficiently.
0 Comments