# Configuring ADS Authentication on Your Service Processors

User Access: Administrators

Use the following example as a starting point when you develop your own script.

This example assumes that the file sp-ips.txt contains a newline delimited list of Service Processor IP addresses. For example:

> 10.10.30.15
> 10.10.30.16
> 10.10.30.17
> 10.10.30.18

The Service Processors have the ability to authenticate users against a Microsoft Active Directory Server. You must first set the clock for each Service Processor against the ADS server and the DNS configuration setup.

> #!/bin/sh

> # This first loop sets up the SPs' DNS configurations
> cat sp-ips.txt | while read ip; do
> ssh $ip sp enable dns --nameserver 10.10.31.1 \
> --nameserver 10.10.31.2 \
> --searchdomain SW-AD-TEST.LOCAL
> done

> # Changing the DNS configuration causes the SSH daemon to restart.
> # Give it time to come back up
> echo Giving SSH daemons time to restart ...
> sleep 15

> cat sp-ips.txt | while read ip; do
> # Assuming our system clock is accurate set the SPs clock against
> # ours. The "sp set date" command requires a UTC date of the
> # form YYYY-MM-DD HH-MM-SS using a 24 hour clock format
> ssh $ip sp set date \"`date --utc "+%Y-%m-%d %H:%M:%S"`\"

> # ADS configuration requires a pre-fabricated keytab file to exist
> # on the SP. Since we have a trusted host setup, we can scp from
> # the client without a login
> scp sp.keytab $ip:/home/manager

> # Now setup ADS
> ssh $ip access enable service ads \
> --keytab /home/manager/sp.keytab \
> --ou "cn=Users,dc=SW-AD-TEST,dc=LOCAL" \
> --server sw-test-dc \
> --domain SW-AD-TEST.LOCAL \
> --logon aserver-sp

> # Remove keytab
> ssh $ip rm -f /home/manager/sp.keytab
> done

Related Topics

Configuring Shell Scripts

Configuring the Client for Scripting

Configuring Multiple Systems for Scripting