All websites now require a system (service) user (v.24, breaking change)

All web sites have an internal initialization part, started right after the very first user request, on behalf of the authorized user.

There was a occasional, yet known issue that occured when the particular (very first) user had a spefic set of limited permissions.

As a result, the web site couldn't initialize itself correctly.

Starting with v.24 all web sites are now:

  1. Requiring a system (service) user, othwerwise they won't start.
  2. Initializing via their system (service) user, defined in their corresponding trusted application.

This change ensures consistent and unambiguous behavior across all web sites.

Why this is considered a breaking change?

There're some specific scenarios, where you can experience an issue, related to this behavior change.

  1. You have manually removed the system (service) user from an web site trusted application.

    In this case your web site won't start.

  2. Your web site trusted application definition contains some limited user.

    Until now, the initialization was relying on the very first user, using this web site. And if it's "powerful" enough - you wouldn't notice any issues. But now, this will be performed only by the system (service) user set.

No manual action needed

This change is managed by an automated update after your instance is updated.

Consequently, if the trusted application related to an site lacks a system (service) user, it will be automatically filled with the default one- `<SYSTEM-APPLICATION-USER>`, removing the necessity for any extra actions on your part.

However, what to do if this change affects me?

Just change the system (service) user of all web sites in their corresponding trusted application to the default one - `<SYSTEM-APPLICATION-USER>`.


More information is available in our official documentation:

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk