Info: The described step can only be performed on the on-premise version of Studio, not on the cloud version.
When a user logs in to Studio, data is loaded that Studio requires to operate. This data is stored in the local storage location of the Web browser in which Studio is run. This data is also accessed when a user reloads a Studio page.
A big part of the information that is stored by Studio is the logon response from Studio Server. The information in this response tells Studio to which Brands the user has access, which Issues, Categories, or Editions are part of each Brand, which access rights the user has, and much more.
Especially for users who have access to many Brands (such as system administrators), the size of the logon response file could exceed the local storage limitation of 5MB. When this is the case, Studio stops working.
For scenarios in which the logon response file is bigger than 5MB, the data can be stored in memory instead.
This is done by setting the following option:
Note: Enabling this option for scenarios in which the logon response file is smaller than 5MB has no benefits.
- File: config.js file
- Name of option: AUTH_INFO_IN_MEMORY
- Value: true or false
How it works
When Studio is (re)loaded with the feature enabled, the logon data is obtained in the following ways and order:
|1||Studio is open.||Logon data is obtained from another tab in the same Web browser in which Studio is running.|
|2||Studio is connected to Studio Server.||Logon data is obtained automatically from Studio Server.|