AD LDS & ADAM do not have have userAccountControl attribute present.

[affrae]

Why:

We have a feature when using a LDAP service (and our documentation discusses this) where you can use LDAP Sync with Active Directory (AD) to suspend and unsuspend users from GHES depending on the account status in AD.

However this feature only works if the userAccountControl attribute is present in the the Active Directory schema. For some flavours of AD, such as AD LDS / ADAM, this attribute is not present in a user record, instead the msDS-UserAccountDisabled provides the appropriate data to work from.

This is causing confusion and pain amongst customers who would like to use LDAP Sync and take our documentation to infer that all flavours of Active Directory are supported.

The PR is to update our LDAP Sync docs to clarify that AD LDS & ADAM do not have have userAccountControl attribute present.

What's being changed:

Replace

{% note %}

**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`.

{% endnote %}

with

{% note %}

**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, do not have the `userAccountControl` attribute present.

{% endnote %}

Check off the following:

• I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
• For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

• This pull request impacts the contribution experience
  • I have added the 'writer impact' label
  • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Staging	Production	What Changed
content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md	Modified	Original

[ramyaparimi]

@affrae
Thanks so much for opening a PR! I'll get this triaged for review ⚡

[vgrl]

I'll update the branch and get this merged once tests are passing 🍏

[vgrl]

👍

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡