Misc Configurations
Changing Windows User in SigningHub
- If windows authentication is enabled in a connection string, installer will use the Windows logged in user to communicate with database upon clicking the Next button. You are required to enter password because it will be used in Application Pool to set the Identity against this user for all websites.
- By default, the current logged-in user will be configured in the Application Pool Identity. If you wish to run SigningHub Enterprise under a different Windows user, then you need to change it manually as shown in the following screen:
- Note that you have to change the user for the Admin, API, Core and Desktop Web modules.
Local Signing in a Load Balanced Mode
Local Signing will not be available by using State Session. However, if users still require performing Local Signing, then please follow this step manually to enable:
Set the Session InProc by placing mentioned tag in the [SigningHub-Installation-Dir]/web/web.config file of all deployments of SigningHub:
<sessionState mode="InProc" timeout="60" cookieName="SH_ID" />
Once the installation progress is complete for Oracle DBMS, an alert will be displayed before you could click the Finish button.