Skip to main content

Management Console

Axidian Management Console (Management Console) is a web application that runs on the basis of IIS. It allows you to administer the system and user settings.

How to open Management Console
  • In the browser: http(s)://server dns/am/mc
  • In IIS: <machine name>\sites\Default Web Site\am\mc

Set up Management Console:

  1. Install the module.
  2. Create an HTTPS binding in the IIS settings.
  3. Set up authentication.
  4. If required, configure optional settings.

Install Management Console​

System requirements

  1. To install Management Console, run Axidian.ManagementConsole-version number.x64.en-us.msi located at Axidian version number\Axidian Management Console version number.

  2. When the installation is complete, you will be prompted to generate a new IDP certificate. This is an optional setting.

    info

    The certificate is required for authentication in Management Console using Identity Provider. This certificate is not intended for establishing the SSL connection.

    If this certificate was generated earlier, disable the option.

    If this option is enabled, a new self-signed certificate is generated and installed in the Local Machine → Personal certificate store. The certificate is used to encrypt data transmitted between the authentication server and the client application.

Create HTTPS binding​

If during the installation the requirement for SSL certificate is enabled in the IIS settings, you must create an HTTPS binding as follows:

  1. In IIS Services Manager, in the left menu, navigate to Axidian Access → sites → Default Web Site.
  2. In the Actions section of the right menu, click Bindings.
  3. Click Add and set the following parameters in the window that appears:
    • In the Type field, select https.
    • In the Port field, specify 443.
    • In the SSL Certificate field, select the Core Server certificate.
  4. Click OK to save the link.

If you do not plan to use the HTTPS protocol, disable the SSL certificate requirement in the IIS settings for Management Console.

Also, in C:\inetpub\wwwroot\am\mc\Web.config, change the value of the requireSSL parameter to false as follows:

<httpCookies httpOnlyCookies="true" requireSSL="false" />

Configure authentication​

You can set different authentication methods to log in to Management Console.

Authentication using Windows Authentication​

To set up authentication using Windows Password, enable Windows Authentication and edit the console configuration file.

Enable Windows authentication​

  1. Open IIS Services Manager and in the left menu, expand the Axidian Access → sites → Default Web Site → am → mc node.
  2. Click Authentication.
  3. Turn on the Impersonation ASP.NET and Windows authentication. Disable all other authentication methods.

Modify the configuration file​

  1. Open C:\inetpub\wwwroot\am\mc\Web.config for editing.
  2. In the amAuthServer section, in the Url parameter, specify the address for connecting to Core Server, such as http(s)://full_dns_name of the server/am/core/.
<amAuthServer Url="https://amcore.test.local/am/core/">
  1. In the LogServer section, in the Url parameter, specify the address for connecting to Log Server, such as http(s)://full_dns_name of the server/ls/api.
<logServer Url="http://amcore.test.local/ls/api/">

If multiple servers are used, specify the address of the load balancer.

  1. Save the changes and restart the IIS server.

Management Console will be available at: http(s)://full_dns_name of the server/am/mc/.

Note

To ignore server certificate errors when logging in to the console, in C:\inetpub\wwwroot\am\mc\Config\applicationSettings.config change the value of the isIgnoreCertErrors parameter to true.

Optional settings​

Set the session lifetime​

To change the session lifetime in Management Console, perform the following steps:

  1. Open C:\inetpub\wwwroot\am\mc\Config\applicationSettings.config.
  2. Set the required value for the sessionExpirationTimeInMinutes parameter. The default value is 30 (minutes).
    <amApplicationSettings
    findUsersMaxResultCount="200"
    isIgnoreCertErrors="false"
    sessionExpirationTimeInMinutes="60"
    allowOverrideRandomPasswordGeneration="false"
    />
  3. Save the changes.

You can configure user search in Management Console by the following parameters:

  • By first name
  • By last name
  • By login
  • By the user name in the Active Directory catalog
  • By first name and last name

To configure the search:

  1. Open C:\inetpub\wwwroot\am\mc\Config\userSearchSettings.config.
  2. In the searchTemplate parameter, specify the search template. Examples of valid templates: **{0}, {0}*, *{0}**.
  3. Enable or disable the search by the following parameters by setting the value to true or false:
    • searchByGivenName: Search by first name. The default value is true.
    • searchBySn: Search by last name. The default value is true.
    • searchByUpn: Search by login. The default value is true.
    • searchByGivenNameAndSn: Search by first name and last name. The default value is true.
    • searchByName: Search by the name displayed in the list of users in Active Directory. The default value is true.

For convenience, you can use templates:

Request exampleComment
john*Depending on your settings, searches for a user whose first name, last name, login, first name and last name, or user name in AD starts with "john".
*oh*Depending on your settings, searches for a user whose first name, last name, login, first name and last name, or user name in AD contains "oh" at the beginning, in the middle, or at the end.
*ohnDepending on your settings, searches for a user whose first name, last name, login, first name and last name, or user name in AD ends with "ohn".
johnA request without * is converted to the template specified in the searchTemplate parameter. If searchTemplate is not specified, * is added to the request on both sides.
**john ** john**Examples of invalid requests. They return no search results.

Display/hide version number in Management Console​

To hide the information about the platform and the version the application was developed on from the API response, perform the following actions:

  1. Open the Management Console configuration file C:\inetpub\wwwroot\am\mc\Web.config.
  2. Depending on the version of IIS:
    • For IIS 10: In the security section, move the comment <!--<requestFiltering removeServerHeader="true" >--> from the second line to the third one.
      <security>
      <requestFiltering>
      <!--<requestFiltering removeServerHeader="true" >-->
      <requestLimits maxAllowedContentLength="104857600" />
      </requestFiltering>
      </security>
    • For IIS above version 10, perform the following actions:
      • Install the URL Rewrite module.
      • Add the following lines to the system.webServer section of C:\inetpub\wwwroot\am\mc\Web.config:
        <rewrite>
        <outboundRules>
        <rule name="replace server header" patternSyntax="Wildcard" lockItem="false">
        <match serverVariable="RESPONSE_SERVER" pattern="*" />
        <action type="Rewrite" value="MyServer" />
        </rule>
        </outboundRules>
        </rewrite>
  3. Save the changes and restart IIS.

Configure logout using Identity Provider​

To configure logout from Management Console using Identity Provider:

  1. Open the console configuration file C:\inetpub\wwwroot\am\mc\Web.config.

  2. In the amAuthentication section, add the enableLogout parameter with the true value.

    <amAuthentication mode="Saml" loginUrl="https://amcore.test.local/am/idp/" enableLogout="true"/>
  3. Open the Identity Provider configuration file app-settings.json located in C:\inetpub\wwwroot\am\idp.

  4. In the PartnerServiceProviderConfigurations section, in the SingleLogoutServiceUrl parameter, specify the address of the server with the Management Console component in the format http(s)://full_dns_server_name/am/mc/Account/SLOService.

    "PartnerServiceProviderConfigurations": [
    {
    ...
    "SingleLogoutServiceUrl": "https://amcore.test.local/am/mc/Account/SLOService",
    ...
    ]
    }
  5. Save the changes and restart IIS.