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.
- In the browser: http(s)://server dns/am/mc
- In IIS: <machine name>\sites\Default Web Site\am\mc
Set up Management Console:
- Install the module.
- Create an HTTPS binding in the IIS settings.
- Set up authentication.
- If required, configure optional settings.
Install Management Console
To install Management Console, run Axidian.ManagementConsole-version number.x64.en-us.msi located at Axidian version number\Axidian Management Console version number.
When the installation is complete, you will be prompted to generate a new IDP certificate. This is an optional setting.
infoThe 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:
- In IIS Services Manager, in the left menu, navigate to Axidian Access → sites → Default Web Site.
- In the Actions section of the right menu, click Bindings.
- 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.
- 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.
- Windows Authentication
- Identity Provider
Authentication using Windows Authentication
To set up authentication using Windows Password, enable Windows Authentication and edit the console configuration file.
Enable Windows authentication
- Open IIS Services Manager and in the left menu, expand the Axidian Access → sites → Default Web Site → am → mc node.
- Click Authentication.
- Turn on the Impersonation ASP.NET and Windows authentication. Disable all other authentication methods.
Modify the configuration file
- Open C:\inetpub\wwwroot\am\mc\Web.config for editing.
- In the
amAuthServersection, in theUrlparameter, 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/">
- In the
LogServersection, in theUrlparameter, 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.
- Save the changes and restart the IIS server.
Management Console will be available at: http(s)://full_dns_name of the server/am/mc/.
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.
Authentication using Identity Provider
To set up a secure login to Management Console using Identity Provider:
- Install and configure the Identity Provider module.
- Install and configure an authentication provider.
- Set up authentication in IIS Service Manager.
- Edit the Management Console and Identity Provider configuration files.
You can also configure logging out of Management Console using Identity Provider.
Set up authentication
- In IIS Services Manager, in the left menu, expand the Axidian Access → sites → Default Web Site → am → mc node.
- Click Authentication.
- Enable options Anonymous authentication and Authentication using forms. Disable all other authentication methods.
Change the Management Console configuration file
- Open C:\inetpub\wwwroot\am\mc\Web.config for editing.
- In the
amAuthServersection, in theUrlparameter, 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/">
- In the
LogServersection, in theUrlparameter, 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.
Make the following changes in the
amAuthenticationsection:In the
modeparameter, specify theSamlvalue.In the
loginUrlparameter, specify the Identity Provider address, such as http(s)://full_dns_name of the server/am/idp/.<amAuthentication mode="Saml" loginUrl="https://amcore.test.local/am/idp/>In the
identityProviderCertificateThumbprintparameter, specify the fingerprint of the Identity Provider certificate.Get-Childitem Cert:\LocalMachine\My\ | Where-Object {$_.Subject -eq "CN=idp"}TipIf Identity Provider and Management Console are installed on different servers, export the certificate without the private key from the server with the Identity Provider module to the server with Management Console. Add the certificate to the certificate store in the Local Machine → Personal section.
In the
serviceProviderCertificateThumbprintparameter, specify the fingerprint of the Management Console certificate that was generated during the installation. The certificate is installed in the Local Machine → Personal certificate store with the common namemcsp.Get-Childitem Cert:\LocalMachine\My\ | Where-Object {$_.Subject -eq "CN=mcsp"}
Save the changes and restart IIS.
Management Console will be available at: http(s)://full_dns_name of the server/am/mc/.
To ignore server certificate errors when logging in to the console, change the value of the isIgnoreCertErrors parameter to true in the C file.:\inetpub\wwwroot\am\mc\Config\applicationSettings.config.
Change the Identity Provider configuration file
Open C:\inetpub\wwwroot\am\idp\app-settings.json for editing.
In the
PartnerServiceProviderConfigurationssection, make the following changes:In the
SingleLogoutServiceUrlparameter, specify the address of the server with the Management Console component installed, such as http(s):/full_dns_name of the server/am/mc/Account/SLOService.In the
Thumbprintparameter, specify the fingerprint of the Management Console certificate that was generated during the installation of the package.TipIf Identity Provider and Management Console were installed on different servers, export the certificate without the private key from the server with Management Console to the server with the Identity Provider module. Add the certificate to the certificate store in the Local Machine → Personal section.
Get-Childitem Cert:\LocalMachine\My\ | Where-Object {$_.Subject -eq "CN=mcsp"}
Example
"PartnerServiceProviderConfigurations":
"Name": "urn:axidianid:emc",
//highlight-grey-next-line
"SingleLogoutServiceUrl": "https://server.axidian.local/am/mc/Account/SLOService",
"PartnerCertificates":
//highlight-grey-next-line
"Thumbprint": "C77EDF29EA05B468BDAF553DE3D804DA4B139C1E"
- Save the changes and restart IIS.
Optional settings
Set the session lifetime
To change the session lifetime in Management Console, perform the following steps:
- Open C:\inetpub\wwwroot\am\mc\Config\applicationSettings.config.
- Set the required value for the
sessionExpirationTimeInMinutesparameter. The default value is 30 (minutes).<amApplicationSettings
findUsersMaxResultCount="200"
isIgnoreCertErrors="false"
sessionExpirationTimeInMinutes="60"
allowOverrideRandomPasswordGeneration="false"
/> - Save the changes.
Configure user search
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:
- Open C:\inetpub\wwwroot\am\mc\Config\userSearchSettings.config.
- In the
searchTemplateparameter, specify the search template. Examples of valid templates: **{0}, {0}*, *{0}**. - Enable or disable the search by the following parameters by setting the value to
trueorfalse:searchByGivenName: Search by first name. The default value istrue.searchBySn: Search by last name. The default value istrue.searchByUpn: Search by login. The default value istrue.searchByGivenNameAndSn: Search by first name and last name. The default value istrue.searchByName: Search by the name displayed in the list of users in Active Directory. The default value istrue.
For convenience, you can use templates:
| Request example | Comment |
|---|---|
| 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. |
| *ohn | Depending 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". |
| john | A 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:
- Open the Management Console configuration file C:\inetpub\wwwroot\am\mc\Web.config.
- Depending on the version of IIS:
- For IIS 10: In the
securitysection, 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.webServersection 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>
- For IIS 10: In the
- Save the changes and restart IIS.
Configure logout using Identity Provider
To configure logout from Management Console using Identity Provider:
Open the console configuration file C:\inetpub\wwwroot\am\mc\Web.config.
In the
amAuthenticationsection, add theenableLogoutparameter with thetruevalue.<amAuthentication mode="Saml" loginUrl="https://amcore.test.local/am/idp/" enableLogout="true"/>Open the Identity Provider configuration file app-settings.json located in C:\inetpub\wwwroot\am\idp.
In the
PartnerServiceProviderConfigurationssection, in theSingleLogoutServiceUrlparameter, 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",
...
]
}Save the changes and restart IIS.