Service Location and Deployment Configuration - Unity Client - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Unity Client

Unity Client
Foundation 23.1

After clicking Next on the Package Extraction or General Settings dialogs, the Service Location dialog is displayed.

  1. Select an existing Service Location or click Add to create a new service location.
  2. Update or enter in the Display Name field the name of the service location for the instance.
  3. Update or enter in the Service Path field the full URL to the OnBase application server service. For example, https://machinename/AppServer/Service.asmx.
  4. Update or enter in the Data Source field the data source name for the appropriate data source.
  5. Select Use NT / LDAP Authentication if your system uses Active Directory or LDAP Authentication.

    In order to use Active Directory or LDAP authentication, the database against which Unity Client runs must also be configured for Active Directory or LDAP authentication. The installer configures Unity Client to match the authentication scheme of the database.

  6. Select Use ADFS if your system uses AD FS (Active Directory Federation Services) authentication.

    Selecting Use ADFS causes the remainder of the deployment to be run in Advanced Mode, even if Advanced Mode was not selected initially, because the configuration file for the module must be updated before signing and finalizing the deployment.


    Use ADFS is not the same Active Directory authentication scheme as Use NT/LDAP Authentication. The Use ADFS option is not available for all modules. If this option is not displayed, the module you are installing either does not support AD FS or must be manually configured for AD FS authentication. You cannot enable both Use ADFS and Use NT/LDAP Authentication. For details on configuring OnBase to use AD FS, see the Legacy Authentication Methods module reference guide.

  7. Click Next to proceed to the Deployment Signing dialog box.

    Depending on the module being updated or added, you may be required to complete information in additional dialogs specific to the module. See the main installation steps above for information on any additional dialogs or steps that must be completed before signing the deployment.

  8. At the Deployment Signing dialog, select the appropriate signing method.

    When Sign from Test Certificate is selected, a test certificate with the Common Name localhost is used. This test certificate is packaged with all ClickOnce installers. For security purposes, it is strongly recommended that this certificate remain un-trusted. This does not mean the certificate cannot be used, simply that when users attempt to launch the ClickOnce link, they are prompted with a message stating that the publisher could not be verified.

    When Sign from Certificate User Store is selected, certificates from the current user store are listed under this option. If there are any certificates in the current user store, they can be used for signing here. Only certificates purposed for code signing are valid.

    When Sign from File is selected, the deployment is signed using the PFX file entered in the corresponding field. Only certificates purposed for code signing are valid.


    Any necessary changes to the files in the deployment folder or the contents of the deployment folder, such as custom changes to the *.config file for the module, must be made before clicking Next at the Deployment Signing dialog box. If you are not in advanced mode, you must access the files directly by navigating to the deployment location before clicking Next and signing the deployment.

  9. Click Next. If you are in Advanced Mode, the File Edit Notification dialog box is displayed.

    From this dialog box you can open the deployment folder by clicking Open Deployment Folder. At this time, any necessary changes to the files in the folder or the contents of the folder should be made. Upon clicking OK, the folder is signed and cannot be modified without updating the deployment instance. Clicking Cancel returns you to the signing screen.

  10. Click OK. The application is deployed and the Summary dialog is displayed upon completion.

    Clicking the link provided under Success launches the application. This is the same as the full path that external users must use to install and launch the application.

    Click Copy Link To Clipboard to copy this link to the clipboard.

  11. Click Finish.