Skip to main content

User management with connection to active directory

Start by defining the AD Domain under General Settings > NodeGraph.

Example: Write DOMAINname if you login with DOMAINname\Username

If you want to use a subset of an AD domain, fill in the AD container field.

Click save.

User Management with Active Directory

The General Settings and NodeGraph tabs in NodeGraph Settings. The fields for Ad Domain and Ad Container are highlighted.

To turn on User Management for Active Directory, make sure there is a user account to log into after it has been runed on.

  1. Create a domain user as Admin, where the username should include your domain.

    • Example: DOMAINname\username

  2. Turn on User Management in the config file (NodeGraphServer.exe.config found in the default folder C:\Program Files\NodeGraph.

  3. Copy the file on your desktop and open it.

  4. Scroll towards the bottom of the script and find the authorization setting:

    <add key="Authentication" value="None" />

  5. Change “None” to “NTML”.

  6. Change server key on:

    <add key="NtlmUrl" value="http://localhost:4115/ntlm/token" />

  7. Replace localhost with the server name where NodeGraph is installed.

  8. Save your changes and copy the file back to its original location.

  9. Restart the NodeGraph service and update the browser.

  10. Verify the NodeGraph service account.

    • To be able to search for users and groups within Windows AD, the service account running NodeGraph must have the right to read and search in Windows AD.

Information noteNodeGraph User Management works with either Windows Active Directory or with the built-in NodeGraph Internal User Management. The Internal User Management can coexist with the Active Directory User Management. If Internal User Management is active and later changed to Active Directory User Management, note that all users created prior to the change will still be able to log in using the link: http://localhost:4114/#/access/signin

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!