The following two methods could be used to perform change the database credentials of SigningHub:


Change Database Credentials via SigningHub Installer

Database credentials stored by SigningHub and ADSS Signing Server are encrypted for security purpose. If you need to make any changes in your database server configurations, then these changes must be reflected in the SigningHub and ADSS Signing Server installations for the signing operations to continue. 


Visit Ascertia's Partner Portal for instructions to change ADSS Signing Server database credentials.


SigningHub provides an option through the installer to update the following types of database related information:

  1. Database username and password
  2. Database name and/or server (in case if database is restored from production database otherwise you need to install with existing database option)
  3. Authentication types (from SQL Server to Windows authentication and vice versa)


Follow the installation wizard until the Installation Type screen is shown: 

 



Click the Next button to show the License Agreement: 



Click the I Agree button to proceed.  


The following screen to prompt for database details is displayed:


 


  1. Username and Password must not contain the following characters: [] \ {} () , : ? * = ! @ | <> = ; ' "" & . These characters are used to either initialize a connection or separate connection values and few are not allowed in XML. For Microsoft SQL Server reference see the  link , for Oracle reference see the link .


Click the Next button to update the database configurations.





Change Database Credentials via XML


Silent installation via XML refers to a method of installing SigningHub silently or without user interaction using an XML file as a configuration or parameter file. In this approach, the installer reads instructions from an XML file to perform the installation without requiring any user input. Given below is a list of parameters to be configured for changing the database credentials via XML. Click here, for a detailed breakdown of each component in the XML file, indicating its purpose, and visibility settings for a silent installation scenario.


  • Welcome
  • System Requirements
  • Installation Type (The mode of installation should be set to "CHANGE_DATABASE")
  • License Agreement 
  • Database Configurations
  • Installation Progress


  1. For a silent installation via XML, set the visibility for all tags to 'false'.



See also