Yes. Connect Daily has a comprehensive security system that gives you control over who can see which calendars.

The easiest way to control this is to go to the Setup Public Calendar Viewing screen and use the mover to control what calendars are visible to the public.

If you want the public to be able to view calendars without logging in, go to the Setup Public Calendar Viewing screen.

Use the Make Super User Screen, located under SYSTEM | SECURITY on the menu.

By default, if you call the View.html page, you can view the calendar without being logged in.

If you're taken to a login screen, you can use the Setup Public Calendar Viewing screen to enable public calendar viewing.

In the SYSTEM | CONFIGURATION | SECURITY screen, delete the PUBLIC USER NAME value and click on SAVE CHANGES.

The simplest way to do this is to go to the Setup Public Calendar Viewing Screen.

See Also: Permissions for Anonymous Users (Permissions for Anonymous Users, User Preferences)

By default Connect Daily stores passwords in a hashed format. This is done to protect the passwords if the database should be compromised. Sometimes, for integration or technical support reasons, customers want to store the plain text passwords. To do this, add the line:

AuthenticationProvider=com.mhsoftware.cdaily.support.security.AuthProviderDefault

to the configuration.properties file. If you have any existing passwords stored in the database, you will need to put in plain text passwords by editing the Users' table. To edit the Users' table, you will have to use a database tool that lets you directly edit the Users' table or use SQL Update commands to set the passwords. For example:

Update users set password='Admin' where user_name='Admin'

You can run individual update statements via the SQL Command Window utility available in the Database configuration screen.

There are three ways to do this:

1. Use container authentication/Windows Integrated Authentication. The container (web server) and the browser will transparently log the user in with no action. Container security configuration is documented here.
2. If you have an existing web application or other system the user is authenticated to, you can use Cookie Signon authentication for single-signon. Cookie based single signon is documented here.
3. You can use plain text passwords. See below for information on how to do this.

Plain Text Password Configuration

The first step is to read the FAQ entry:

How can I configure for plain text passwords?

Once you have followed these steps, create your link in the form:

http://hostname/CALENDAR_PATH/login.html?txtUserID=USER_NAME&txtPassword=PASSWORD&btnSubmit=Login

For hosted Users the CALENDAR_PATH portion would not be present. The URL would be something like:

http://calendar.yourdomain.com/login.html?txtUserID=USER_NAME&txtPassword=PASSWORD&btnSubmit=Login&target=ViewCal.html&calendar_id=11

Replace the USER_NAME value with the name of the User you would like to have the person be logged in under.

Replace the PASSWORD value with the password for the User account you are logging in with.

The page specified by target will be invoked and all parameters not relating to login will be passed as part of the request.

See Also: Calendar Display Arguments