Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit d3c79ef

Browse files
Update master-data-services-installation-and-configuration.md
Adding additional requirement for the MDS App pool identity account. This was discussed with the MDS PG team and updated here.
1 parent edee654 commit d3c79ef

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/master-data-services/master-data-services-installation-and-configuration.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -191,6 +191,9 @@ If you're interested in making changes to the installation of [!INCLUDE[ssnovers
191191
> [!NOTE]
192192
> If your domain implement [2020 LDAP channel binding and LDAP signing requirements for Windows](https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows). You will see issue "The credentials could not be verified in Active Directory." when you using domain account to create Application Pool. For workaround, instead of domain user, use a **local machine user**. This can bypass the credential checking with Active Directory. After creating the web application, you can change the identity to domain user in **Internet Information Services (IIS) Manager**.
193193
194+
> [!NOTE]
195+
> Your MDS Application Pool Identity must be a part of Windows Authorization Access Group.
196+
194197
12. On the **Web Configuration** page in the **Web application** box, click the application you've created, and then click **Select** in the **Associate Application with Database** section.
195198

196199
13. Click **Connect**, select the [!INCLUDE[ssMDSshort](../includes/ssmdsshort-md.md)] database that you want to associate with the Web application, and then click **OK**.

0 commit comments

Comments
 (0)