Using your Web Server to Validate Users

Calcium security depends on identifying users using a username and password. Normally, the login capabilities built-in to Calcium are used. It is possible, however, to configure your web server to request a username and password instead of using the Calcium login screen.

Note that the web server will only provide authentication - that is, it will only ensure that the user is who they claim they are. You will still need to add the user to Calcium and set privileges for the user in the security page for each calendar (or possibly assign them System Administration rights).

Since the web server is configured to require a username and password, people won't be able to use Calcium at all unless they log in. To get around this restriction and allow Anonymous users, copy the main Calcium script, and give it another name (e.g. CalciumView). Then, configure your web server to allow use of that CalciumView URL without authentication.

On Microsoft Windows systems, server authenticated usernames typically look like "domainname\username". You'll need to use the same thing, including the backslash, for the Calcium username. Although Windows usernames are typically not case sensitive, Calcium usernames are; this means the Calcium username must exactly match the Windows name, including case.