Info: This feature requires Content Station 11.56 or higher. The use of Enterprise Server 10.7 or higher is recommended.
When a user logs in to Content Station, data is loaded that Content Station requires to operate. This data is stored in the local storage location of the Web browser in which Content Station is run. This data is also accessed when a user reloads a Content Station page.
A big part of the information that is stored by Content Station is the logon response from Enterprise Server. The information in this response tells Content Station 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, Content Station 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 Content Station is (re)loaded with the feature enabled, the logon data is obtained in the following ways and order:
|1||Content Station is open.||Logon data is obtained from another tab in the same Web browser in which Content Station is running.|
|2||Content Station is connected to Enterprise Server 10.7.0 or higher.||Logon data is obtained automatically from Enterprise Server.|
Content Station is connected to Enterprise Server 10.6 or lower.
The current session ticket has expired.
|Logon data is obtained from Enterprise Server by forcing the user to log in again.|