New Leopard server installation; no user calendars via Web?

Question

We have just done a clean install and migration of all users from a Mac OS X 10.4 (Tiger) server to a 10.5 (Leopard) one and are trying to figure out how to enable the user calendars.
Have done the step of turning on iCal server, which seemed to be necessary anyway to get the blogs working, and configuring it for SSL with a self-signed cert. Have also enabled calendaring in Workgroup Manager for the users we wish to provide with calendaring. Have also been able to figure out how to subscribe (read-only) to a user or a group calendar, and how to add an account via iCal to get read/write access to a user calendar via the "Preferences... Accounts" method described in other threads.
Why is it, though, that no user calendars or even links to them show up via the "Users" pages on the collaboration-services-driven web pages? Is the calendaring for users in Leopard server set up only to allow access via CalDAV clients, and not display these user calendars in or near the user's web pages, like the one that hosts their blogs? It seems odd that one can view and edit a group calendar via the web, but a user cannot see or edit his or her own calendar in the same way via the web. Did we miss something or do something wrong?

Answer 1

First of all: Don't store passwords. Store a hash of it. E.g. the specialized
Rfc2898DeriveBytes class or a
SHA hash. Make yourself familiar with the concept of salts.
Also important: Don't concat strings to build SQL commands. This is prone to
SQL injection. Use parameterized statments instead of it. E.g.
public DataSet RetrieveUserProfile(string email, string passwordHash)
DataSet result = null;
const string SQL_COMMAND_TEXT = "SELECT * FROM Detailed WHERE Email = @Email AND PasswordHash = @PasswordHash;";
using (SqlConnection connection = Class1.GetConnection())
connection.Open();
using (SqlCommand command = new SqlCommand(SQL_COMMAND_TEXT, connection))
command.Parameters.Add("@Email", SqlDbType.NVarChar);
command.Parameters.Add("@PasswordHash", SqlDbType.NVarChar);
command.Parameters["@Email"].Value = email;
command.Parameters["@PasswordHash"].Value = passwordHash;
using (SqlDataAdapter dataAdapter = new SqlDataAdapter(command))
result = new DataSet();
dataAdapter.Fill(result);
return result;
We are normally using CamelCase as it's C# not Java, thus method names start with upper-case letters. Also Get is a reserved verb like set or do. It's only used for explicit getter methods. Parameter names are started with a lower-case letter.
Use the
using statement for classes which implement IDisposable. So your objects are properly disposed, even when an exception occurs in the inner scope.
And least, but not last: use a layered architecture. The actual WebMethod is only a
facade. So that you can use unit tests. See
Unit Test Basics.
p.s. there must be an
UNIQUE CONSTRAINT on the Email column in your table.