Action items after changing the operator user password when using CAST Console

End of Life Notice

CAST Storage Service (com.castsoftware.css) is End of Life and is no longer supported or distributed. Customers previously using CAST Storage Service must migrate to a standard PostgreSQL installation. CAST recommends PostgreSQL 18.x.

Introduction

The “operator” user password is assumed to be set to “CastAIP”. If this is not the case - i.e. you have manually changed it (see  Changing the default operator and guest passwords for CAST Storage Service) - you will need to perform the actions listed below when using CAST Console. t is not necessary to change the operator password in any .pmx file nor in the  cms_inf_store_css table.

Step 1 - encrypt new password

A plain text password will be accepted, but CAST highly recommends encrypting the password first, see  Using the aip-encryption-tool to encrypt credentials. When the new password has been encrypted, store a copy of the encrypted password in a text file (for example) as it will be required later on in the process.

Step 2 - update PostgreSQL information

Update persistence data schemas

Information about the PostgreSQL instances available to CAST Console for analysis purposes is stored in a PostgreSQL schema in various different tables as listed below. The password is stored in these tables and will need updating:

CAST Console Enterprise edition - host PostgreSQL instance defined during the installation process for Java JAR/Global installers, or for a Docker deployment, in the CSS/PostgreSQL instance provided as a Docker container:

- aip_node.database_connection_settings
- aip_config.properties

For example:

To change the stored password, the recommended method is to run SQL queries, where ENCRYPTED_KEY is the encrypted password generated in Step 1:

CAST Console Enterprise edition

Update .yml files

Additionally, information about the PostgreSQL instances available to CAST Console for analysis purposes is stored in various . yml properties files. The encrypted password is referenced and will also need updating:

CAST Console Enterprise edition:

In each file, search for an entry entitled spring:, datasource:, password: , and then paste in the new password before saving the files:

Step 3 - Update SSO service (2.x enterprise mode only)

Edit the following file with a text editor:

%PROGRAMFILES%\CAST\AIP-SSO\opt\jboss\tools\cli\databases\postgres\change-database.cli

Locate the following entries in the file and replace them with their correct values:

${db.user} e.g. "operator"
${db.password} replace this with the new database password (in clear text, not encrypted!)
${db.host} set the database host value using this format "machine:port" (e.g. "localhost:2284")
${db.database} set to the keycloak database name (e.g. "keycloak")

Open a CMD prompt with elevated privileges, e.g. right click and “Run as administrator and run the following .bat file, where admin_user and admin_pass are the credentials for your Keycloak instance - if you have not changed them, the default is admin/admin:

%PROGRAMFILES%\CAST\AIP-SSO\opt\jboss\tools\configure.bat -u admin_user -p admin_pass

Step 4 - perform a resync action on all relevant Applications

In CAST Console move to the  **Admin Center**and choose the  Applications tab. Perform a Resync operation on all Applications:

Click to enlarge

Step 5 - update CAST Dashboards

If your CAST Dashboards access any applications stored on a PostgreSQL instance for which you have changed the “operator” user password, you will need to update your configuration, depending on your environment. When you have updated the relevant file, save the file and then restart the web application or Apache Tomcat server.

JAR installer: %PROGRAMDATA%\CAST\Dashboards\<folder>\application.properties
ZIP: deployed_zip\configurations\application.properties

restapi.datasource[0].password=CRYPTED2:90B1A6EC1618661401B724DB5AC34595

CATALINA_HOME\webapps\CAST-RESTAPI-integrated\META-INF\context.xml

<Resource name="jdbc/domains/Resource1" url="jdbc:postgresql://my_css_server:2282/postgres"
username="operator" password="CastAIP"

WAR: CATALINA_HOME\webapps\<dashboards>\WEB-INF\classes\application.properties
ZIP: deployed_zip\configurations\application.properties

restapi.datasource[0].password=CastAIP

CATALINA_HOME\webapps\<dashboards>\META-INF\context.xml

<Resource name="jdbc/domains/Resource1" url="jdbc:postgresql://my_css_server:2282/postgres"
username="operator" password="CastAIP"

Step 6 - update CAST Imaging source code viewer

If you are uploading your applications direct to CAST Imaging and you are using the CAST Imaging source code viewer, you will need to update the configuration to use the new password for the relevant PostgreSQL. You can find out more about this in  Configure the source code viewer.

Step 7 - restart all services

Finally ensure you restart all related services in the following order:

V2 Enterprise mode:

• Console SSO
• Console Service Registry
• Console Gateway
• Console Node
• Dashboards
• Imaging

V2 Standalone mode:

• Console
• Dashboards
• Imaging