Filter
Top Products
Authentication services
Using an Active Directory server
Windows domain
Specify the Windows domain to which the service controller belongs. The service
controller must be part of a Windows domain (mydomain.com, for example) to
authenticate users that belong to that domain.
Check Active Directory access with attribute
Enable this option to have the service controller only accept users with a specific setting
in their account.
Use Active Directory remote access permission: Use the standard attribute
defined in Active Directory for remote access (MsNPAllowDIalin). If this attribute is
set, then the user can be authenticated via Active Directory.
Use LDAP attribute: For non-standard implementation of Active Directory, set this
according to the equivalent setting on the Active Directory server.
Join
Before the service controller can process user authentication using Active Directory, you
must join the service controller with the Active Directory server. Fill in the required
parameters and click Join Realm Now. This is usually a one-time event.
Username
Username the service controller will use to join Active Directory.
Password
Password the service controller will use to join Active Directory.
Note For security reasons, Username and Password are not stored on the service controller.
Join Realm Now
Select to join the realm immediately.
Status
Shows the status of the join operation as follows:
Unknown: System is processing, no status to report. Refresh the page to update the
status.
DNS unavailable: DNS not working, cannot access Active Directory.
Missing Config: No configuration, so join cannot proceed.
Never Joined: Administrator never selected Join Realm Now.
Not joined: Not joined: May be joined with the domain, but the join is not confirmed
yet. Status will change to Joined once confirmed. If the Not Joined status persists,
check connectivity between the service controller and Active Directory or re-join.
Joined: Active Directory reports that service controller successfully joined.
6-10