By default the MacOS X Open Directory debugging log file is disabled. You can temporarily reenable it by running the following command in the Terminal app:
sudo killall -USR1 DirectoryService
After you reboot, debugging will be disabled again. If you want to enable Open Directory debugging so that it stays enabled across reboots, run the following command in the Terminal app:
To disable debugging again just delete that file:
sudo rm /Library/Preferences/DirectoryService/.DSLogAtStart
The debugging log file is located at:
ipsCA is a company that sells SSL certificates. Their SSL certificates are recognized by all the major browsers so you don’t need to worry about manually installing additional Certificate Authority (CA) certificates into your users’ web browsers like you have to do with CA companies whose certificates are not included by default in the major web browsers. What is great about ipsCA is that they offer free 2 year SSL certificates for educational institutions such as Universities. If your domain ends in .edu then you qualify for a free 2 year SSL certificate.
ipsCA certificates are a little unusual in that you need to install two certificates onto your server before it will work. I couldn’t find a documented set of procedures for installing ipsCA certificates on a MacOS X 10.4 server so I wrote some up:
Installing an ipsCA SSL Certificate in OS X 10.4
Generate the CSR
- In Server Admin, select the server you would like to secure.
- Click “Settings” > “Certificates” tab > “Add(+)” button.
- A dialog box will appear to enter your certificate information. Please refer to vs7313 for detailed CSR requirements.
- Enter starting and ending validity dates.
- Select private key bit length size (1024 is recommended and required for three year certificates)
- Enter a passphrase (“password”) for your private key.
- Apple recommends “use at least 20 characters, include mixed case, numbers and/or punctuation, have no characters repeat, and having no dictionary terms.”
- Click “Save”. Now, “Request Signed Certificate From CA” can be selected.
- A dialog box will appear. Drag the certificate icon onto your desktop. This will create your CSR file.
- copy and paste the text of the CSR file into the certificate request form on the ipsCA website.
- Submit the request and wait for ipsCA’s email response.
Import the Signed Certificate
- In Server Admin, select the server the certificate needs to go on.
- Click “Settings” > “Certificates” tab
- Highlight the certificate the signed certificate corresponds to.
- Click the “edit” icon.
- Click the “Add Signed Certificate…” button.
- Paste the contents of the signed certificate text file you received from ipsCA into the text box that appears. Press OK to import the signed certificate.
- Quit and restart the Server Admin app to make sure it refreshes the status of the signed certificate.
- When you try to edit the certificate all the fields should be greyed out to indicate the certificate is signed and the import was successful.
- You may need to redesignate the newly signed certificate in the web server and/or restart it before Apache will start using the newly signed certificate.
Install the ipsCA Intermediate Certificates
1. Copy the ipsCA intermediate certificates bundle file into the /etc/certificates/ directory on the web server. At the time of this writing this file was named “IPS-IPSCABUNDLE.crt. The file is available on the ipsCA website.
2. Change the permissions on the certificate bundle to “640”.
- cd /etc/certificates
- sudo chmod 640 IPS-IPSCABUNDLE.crt
3. Navigate to the folder /etc/httpd/sites/ and locate the .conf file that corresponds to the the SSL virtual host that the certificate belongs to. Usually the filename of the .conf file will be named in the format “someNumber_IPAddress_443_fullyQualifiedHostName.conf”
4. Once you locate the file, open it in a text editor at locate the part of the virtual host section that covers the SSL certificate settings. The section you are looking for will look something like this:
5. Add the following setting in between the “SSLCertificateKeyFile” and “SSLCipherSuite” setting:
- When you are done the certificate section should looking something like this:
6. Save your changes and restart the web service. You should now be able to navigate to your SSL website and receive no “invalid” certificate errors. You can test your web server by using the ipsCA test website at: http://certs.ipsca.com/checkserver/
Symptom: Users are unable to connect to the FTP service on MaxOS X Server 10.4. Both local user accounts and Open Directory users are unable to connect to the server via FTP. However they are able to connect to the server via Apple File Sharing (AFP). The system.log file has FTP server entries which contain “… ACCESS DENIED (not in any class) …” and “… FTP LOGIN REFUSED (access denied) … ”
Solution: The FTP server configuration file has become corrupt. Perform the follow steps to reset the FTP server configurations back to default:
sudo serveradmin stop ftp
sudo mv ftpaccess ~/Desktop
sudo cp ftpaccess.default ftpaccess
sudo serveradmin start ftp
This replaces the ftpaccess file with a fresh clean one without any corruptions. Since this procedure resets all the FTP service settings back to default, you’ll need to reconfigure the FTP service settings to what you had before.
You can read more about this problem at the following Apple Discussion Forums thread: Link
In Mac OS X 10.4 Tiger some system preferences were unique to a particular computer and so were named using a naming convention that included the MAC address of the first network device in the computer (en0). In Mac OS X 10.5 Leopard this naming convention was changed to use a different unique identifier other than the first network adapter’s MAC address. Leopard now uses something called the UUID for this unique identifier. You can determine a UUID of a Leopard computer by running the terminal command:
ioreg -rd1 -c IOPlatformExpertDevice | grep -E '(UUID)'