Skip to content

Setting Up Domains

Mike Garvey edited this page Apr 21, 2022 · 2 revisions

The AD RestAPI can be set to point to multiple domains, even across Forest Trusts if need be.

Prerequisites

  1. Can resolve the domain name through DNS.
  2. Have TCP port 389/636/3268/or 3269 access to a Domain Controller in the domain.
  3. The account running the IIS Application Pool has access to the specified domain (read access for Windows Authentication using Kerberos/Negotiate, full access for other authentication schemes).

An example of a domain entry in the appsettings.json file looks like:

"contoso.com": {
    "IsDefault": true,
    "IsForestRoot": true,
    "DistinguishedName": "DC=contoso,DC=com",
    "StaticDomainController": "",
    "UseGlobalCatalog": false,
    "UseSchemaCache": true,
    "UseSSL": true
}

The key name is the FQDN of the domain that can be contacted. As long as the '$schema' entry of the appsettings.json file is set to 'https://raw.githubusercontent.com/Yevrag35/AD-RestAPI/master/AD.Api-NET6/Schemas/AD.Api-appsettings_schema.json', you can open the json file in VSCode or Visual Studio to verify the schema.

*NOTE* - In the Beta builds here, only Forest root domains are supported (because of the Schema querying and attribute validation).

Clone this wiki locally