Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Some things to be aware of:

  • This feature is in beta and MUST NOT be used if you have re-used an existing authorizations.xml file with the new deployment and this file contains authorizations defining specific "restrictions" or which define "application name patterns". In this case, the user interface must not be used and instead authorizations and roles must be updated using the REST API (see /server/authorizations and /server/roles web services).
  • This new management interface relies on a new schema hosted on a CAST Storage Service/PostgreSQL instance to store the roles/data authorizations. This schema is called cast_dashboards by default and will be created on first startup of the web application. You will need to specifically configure a connection in the file to a CAST Storage Service/PostgreSQL instance which will be used to host the schema. This instance does not need to be the same as used for your AIP schemas (Dashboard/Measure schemas), however, the required schema is small and therefore CAST recommends using an existing CAST Storage Service/PostgreSQL instance to host it. The schema is created automatically when you start up your Dashboard deployment if it does not already exist. You can find out more information in Step 6 and 8 and  in the following documentation:
  • The cast_dashboards schema can be re-used across multiple dashboard deployments if your roles/authorization requirements are the same for all deployed dashboards
  • If the cast_dashboards schema already exists on the referenced CAST Storage Service/PostgreSQL instance, it will not be recreated and any roles/authorizations defined in it will be re-used
  • When using a combined Health and Engineering Dashboard deployment, the cast_dashboards schema and all roles and authorizations defined in it are valid for both dashboards
  • You can use an alternative name for the cast_dashboards schema, for example if you are deploying multiple standalone dashboards but require different roles/authorizations assignments in each dashboard. See Changing the name of the cast_dashboards schema.
  • If you are using a RESTRICTED license key for access to the Dashboard schema (see Data authorization - 2.x and above and also Dashboard Service license key configuration): 
    • AND a standalone Engineering Dashboard any authorizations must still be defined in the license.xml file.
    • AND a combined Engineering/Health Dashboard, any authorizations for the Engineering Dashboard must still be defined in the license.xml file and any authorizations for the Health Dashboard must be defined in the new management interface
  • Authorizations for tags/categories and restrictions are not supported in the new management interface
  • If you are moving from a previous 1.x or 2.0 release (see Standalone Dashboard upgrade) and have a set of roles/authorizations you wish to retain, you have two choices:
    • You can provide your roles.xml and/or authorizations.xml file and on first start-up of the web application the role assignments will be automatically transferred into the management interface. The roles.xml/authorizations.xml file will then be ignored on any subsequent web application startup and all changes from then on must be performed using the graphical interface.
    • You can assign the roles from scratch using the graphical interface.
  • Any changes made in the interface to assigned roles are only taken into account when the user logs out and logs back in again. Data authorizations are effective immediately.