Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Identity Manager 8.1.4 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Using scripts Notes on message output Notes on using date values Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing of scripts in Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for executing scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Installing and configuring the SOAP Web Service

To install the SOAP Web Service, you must provide a server on which the following software is already installed:

  • Windows operating systems

    The following versions are supported:

    • Windows Server 2008 R2 (non-Itanium based 64-bit) service pack 1 or later

    • Windows Server 2012

    • Windows Server 2012 R2

    • Windows Server 2016

    • Windows Server 2019

  • Microsoft .NET Framework Version 4.7.2 or later

  • Microsoft Internet Information Services 10, 8.5, 8, 7.5, or 7 with ASP.NET 4.7.2, and the Role Services:
    • Web Server | Common HTTP Features | Static Content

    • Web Server | Common HTTP Features | Default Document

    • Web Server | Application Development | ASP.NET

    • Web Server | Application Development | .NET Extensibility

    • Web Server | Application Development | ISAPI Extensions

    • Web Server | Application Development | ISAPI Filters

    • Web Server | Security | Basic Authentication

    • Web Server | Security | Windows Authentication

    • Web Server | Performance | Static Content Compression

    • Web Server | Performance | Dynamic Content Compression

Required permissions
  • The user account that the Internet Information Service runs under, needs write access (MODIFY) to the installation directory.

  • The following permissions are required for automatic updating:

    • The user account for updating requires write permissions for the application directory.

    • The user account for updating requires the local security policy Log on as a batch job.

    • The user account running the application pool requires the local security policies Replace a process level token and Adjust memory quotas for a process.

Detailed information about this topic

Installing the SOAP Web Service

IMPORTANT: Start the SOAP Web Service installation locally on the server.

To install the SOAP Web Service

  1. Launch autorun.exe from the root directory of the One Identity Manager installation medium.

  2. Go to the Installation tab and select the entry Web based components and click Install. Starts the Web Installer.

  3. On the start page of the Web Installer, select Install SOAP Web Service and click Next.

  4. On the Database connection page, enter the connection data for the One Identity Manager database and click Next.

  5. On the Select setup target page, configure the following settings and click Next.

    Table 188: Settings for the installation target
    Setting Description
    Application name Name used as application name, as in the title bar of the browser, for example.
    Target in IIS Internet Information Services web page on which to install the application.
    Enforce SSL Specifies whether insecure websites are available for installation. If the option is set, only sites secured by SSL can be used for installing. This setting is the default value. If this option is not set, insecure websites can be used for installing.

    URL

    The application's Uniform Resource Locator (URL).

    Install dedicated application pool

    Specifies whether an application pool is installed for each application. This allows applications to be set up independently of one another. If this option is set, each application is installed in its own application pool.

    Application pool

    The application pool to use. This can only be entered if the Install dedicated application pool option is not set.

    If you use the DefaultAppPool default value, the application pool has the following syntax:

    <application name>_POOL

    Identity

    Permissions for executing an application pool. You can use a default identity or a custom user account.

    If you use the ApplicationPoolIdentity default value, the user account has the following syntax:

    IIS APPPOOL\<application name>_POOL

    You can authorize another user by clicking ... next to the box, enabling the Custom account option and entering the user and password.

    Web authentication

    Specifies the type for authentication against the web application. You have the following options:

    • Windows authentication (single sign-on)

      The user is authenticated against the Internet Information Services using their Windows user account and the web application logs in the employee assigned to the user account as role-based. If single sign-on is not possible, the user is diverted to a login page. You can only select this authentication method if Windows authentication is installed.

    • Anonymous

      Login is possible without Windows authentication. The user is authenticated against the Internet Information Services and the web application anonymously, and the web application is directed to a login page.

    Database authentication

    NOTE: You can only see this section if you have selected a SQL database connection on the Database connection page.

    Specifies the type for authentication against the One Identity Manager database. You have the following options:

    • Windows authentication

      The web application is authenticated against the One Identity Manager database with the same Windows user account that your application pool uses. Login is possible with a user-defined user account or a default identity for the application pool.

    • SQL authentication

      Authentication is completed with a SQL Server login and password. The SQL Server login from the database connection is used. Use the [...] button to enter a different SQL login, for example, if the application is executed with a access level for end users. This access data is saved in the web application configuration as computer specific encrypted.

  6. Specify the user account for automatic updating of the application server on the Set update credentials page.

  7. The user account is used to add or replace files in the application directory.

    • Set Use IIS credentials for update, if you want to use the user account that is running the application for updates.

    • Set Use other credentials for updates, if you want to use another user account and enter the domain, user name, and password for the user.

  8. Installation progress is displayed on the Setup is running page. Once installation is complete, click Next.

    The Web Installer generates the web application and the corresponding configuration files (web.config) for each directory.

  9. Click Finish on the last page to end the program.

Configuring the SOAP Web Service

The SOAP Web Service configuration is found in Web.config in the installation directory. You can use any text editor to edit this file.

Table 189: Configurable options in the “web.config” configuration file
Section Option Permitted values Description

connectionString

 

 

Database connection parameter.

runtimedirs

key="Cache"

value = "<path>"

Directory for storing the cache directory.

Default: value="C:\inetpub\wwwroot\<web service name>\App_Data\Cache\DB"

 

key="AssemblyCache"

value = "<path>"

Directory for storing the cache directory.

Default: value="C:\inetpub\wwwroot\<web service name>\App_Data\Cache\Assemblies"

settings

key="timeout"

value="<time>"

Timeout for connections in the application pool.

Default: value="00:05:00"

 

key="maxconnectionlifetime"

value="<time>"

Maximum length of time to maintain the connections. After this time limit has expired, all the connections are closed even if the timeout has not expired yet.

Default: value="00:05:00"

 

key="usepropertybag"

value = "True"

value = "False"

Specifies whether a property bag is used. A property bag is used when object properties are populated in order to maintain the particular fill order that is required because of side effects or templates.

Permitted values are:

  • False: Value are set in the object in the order in which they were given.

  • True: The fill order is determined by the metadata.

Default: value=”True"

 

key="ignoreinvisiblevalues"

value = "True"

value = "False"

Specifies whether values that the user is not permitted to see are not returned.

Permitted values are:

  • False: Values that the user is not allowed to see, generate an error message.

  • True: Values that the user is not allowed to see, are not returned. If this value is set, the user is issued an error message.

Default: value=”True"

 

key = "logdirectory"

value = "<path>"

Log directory.

Default: value = "C:\inetpub\wwwroot\<web service name>\App_Data\Logs

 

key = "allowwebservicemethods"

value = "List of methods"

Semicolon-delimited list of permitted web service methods.

 

key = "allowfunctions"

value = "List of functions"

List of the permitted functions for each CallFunction method. If no other function is given, all functions are permitted.

Related topics

Displaying the SOAP Web Service‘s status

The SOAP Web Service can be reached over a browser under:

http://<server>/<application name>

https://<server>/<application name>

TIP: You can open the web server's status display in the Job Queue Info. In the Job Queue Info, select View | Server state in the menu and, on the Web servers tab, open the web server status display from the Open in browser context menu.

In addition, API documentation is available here.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating