Replacing Database User with Service ID Authentication with OM Web Viewer 12.1

Products

• Output Management Web Viewer

Issue/Introduction

We have an internal compliance requirement to transition from using direct database user accounts to Service ID–based authentication for all application-to-database connections. Our application currently uses a standard database user in the configuration files.

We need to understand whether replacing the existing database user in the application configuration with a Service ID will cause any functional or connectivity impact. Specifically:

Will the application behavior, permissions, or connection handling be affected if we switch to a Service ID?
Are there any dependency changes, configuration updates, or driver-level adjustments needed to support Service ID authentication?
If an impact is expected, what is the recommended approach or migration steps to ensure a seamless transition?

Environment

• OM Web Viewer 12.1
• Microsoft SQL Server 

Resolution

1. Upgrade Web Viewer 12.1 maintenance to build 256 or later, as well as Tomcat to version 9.0.111 or later. This includes the MSSQL Driver version 12.1.8.
2. Configure Active Directory authentication. Refer to the MSSQL documentation here. You should be able to specify the custom connection properties in the {CAOMWV12_HOME}/config/WVProfile.properties file to establish a connection. Web Viewer 12.1 should be able to connect successfully with those properties. 
   
   Important Note: Do not run ConfigTool, as this may override your changes in the WVProfile.properties file.

Refer to the Output Management Web Viewer Supportability Matrix for supported components.