Latest revision as of 12:41, 9 May 2013

Description

This test case verifies an Active Directory client is able to connect to a particular DNS site as defined on the AD server

Verify that your Active Directory domain access works. If you don't have an Active Directory domain, you can set one up.
Run through the test case to join the domain.
Inspect the sssd.conf to ensure that the SSSD would attempt to connect using service discovery only:
```
 ad_servers = _srv_ 
```
More information on AD sites can be found in this technet article

Open dssite.msc MMC
Open Start, Run..

enter dssite.msc
Create a new site and assign a domain controller to the site
In the "Active Directory Sites and Services" MMC, right-click the "Sites" folder

Select "New", "Site.."

Name the new site, select the default IP transport and click OK
Create a new subnet and link it with the site
In the "Active Directory Sites and Services" MMC, right-click the "Subnets" folder

Select "New", "Subnet.."

The subnet must be the same as the client's. It can even match the client's IP address and use the /32 mask.

Link the subnet with the site you just created
Make sure SSSD is up and running
```
 # service start sssd 
```
Force SSSD to connect to the Active Directory, for example using 'getent passwd <account>'

Verify with netstat that the SSSD has connected to the AD server you'd expect it to connect to using netstat:
```
 # netstat -tpn | grep 389 
```
The command above should yield the IP address of the server in the site you specified for the client.

You should make sure to remove the site and the subnet to prevent them from interfering with the rest of the tests.
If you changed the ad_servers directive, revert the change to the original value

This command will print all primary servers found by SSSD. Primary servers are all domain controllers for the client's site.

 # grep "Inserted primary server '.*' to service 'AD'" /var/log/sssd/sssd_AD.log

For example:

 (Mon May  6 08:22:11 2013) [sssd[be[AD.PB]]] [fo_add_server_to_list] (0x0400): Inserted primary server 'ad-server.ad.pb:389' to service 'AD'

@@ Line 9: / Line 9: @@
 |actions=
-# Open dssite.msc MMC (Win+R, mmc dssite.msc)
+# Open dssite.msc MMC
-# Create new site "My-Site" (Action/New site) and assign domain controller
+#: Open Start, Run..
-# Create new subnet (Click on Subnets, Action/New subnet) and link it with the site
+#: enter <code>dssite.msc</code>
+# Create a new site and assign a domain controller to the site
+#: In the "Active Directory Sites and Services" MMC, right-click the "Sites" folder
+#: Select "New", "Site.."
+#: Name the new site, select the default IP transport and click OK
+# Create a new subnet and link it with the site
+#: In the "Active Directory Sites and Services" MMC, right-click the "Subnets" folder
+#: Select "New", "Subnet.."
 #: The subnet must be the same as the client's. It can even match the client's IP address and use the /32 mask.
+#: Link the subnet with the site you just created
 # Make sure SSSD is up and running
 #: <pre> # service start sssd </pre>
-# Force SSSD to connect to the Active Directory, for example by logging in
+# Force SSSD to connect to the Active Directory, for example using 'getent passwd <account>'
 |results=