Server access - required rights
This page requires that you have already read and understood the information in Server access rights - overview.
This page describes the server access rights that are required for the various different processes carried out and managed by the CAST Management Studio when you are using a commercial RDBMS to host the CAST databases.
Connecting to a Management Service when launching the CAST Management Studio
To connect to a CAST Management Service for the purposes of using the CAST Management Studio, the following rights are required:
- Read tables
- Write to tables
- Execute stored procedures
In other words, the user specified in the Connection Profile used when launching the CAST Management Studio (this can be managed via the Manage CAST-MS Connections option) must have at least the above rights.
- The user defined in the Connection Profile automatically created by CAST Server Manager for the Management database/schema will ALREADY have the necessary rights (because the rights required to install the Management Service are sufficient). If you want to use a different user with more restricted rights for your particular "server" environment, use the above list as a guide and modify the login credentials either when you are prompted to verify them (see Launching the CAST Management Studio) or once connected via the Manage CAST-MS Connections option.
- Note that in a CAST Storage Service environment, rights do NOT need to be managed. The default Operator user already has the required rights to connect to a Management Service.
Interaction with an Analysis/Dashboard/Measurement Service during an analysis or snapshot generation
The rights required in each server environment for interaction with an Analysis/Dashboard/Measurement Service using the CAST Management Studio during an analysis or snapshot generation are detailed in the CAST Installation Guide (see http://doc.castsoftware.com)- in a page called Appendix - Login privileges for CAST Products.
- Note that in a CAST Storage Service environment, rights do NOT need to be managed. The default Operator user already has the required rights to interact with an Analysis/Dashboard/Measurement Service
- In an Oracle server environment, if you want to use a user other than the Analysis/Dashboard/Measurement Services owner, you may find that you cannot perform some actions (typically generate a snapshot) and an "insufficient privileges" message will be displayed in the log.
As such and given that the "public" user is automatically granted access to all CAST objects, an Oracle user that wants to connect to a schema that they do not own requires the following privileges:
- a user with correct rights to access their default schema
- CREATE ANY TABLE
- INSERT ANY TABLE
- DELETE ANY TABLE
- UPDATE ANY TABLE
- SELECT ANY TABLE
- SELECT ANY SEQUENCE
- DROP ANY TABLE
- CREATE ANY INDEX
- DROP ANY INDEX
- ANALYZE ANY