Zulu Read Only
(Created page with "Read Only Calendars ==iCal== You'll find a list of read-only versions of your calendar on the Publish page after you publish your file with Zulu (you can re-publish any time ...") |
|||
| Line 18: | Line 18: | ||
:For FileMaker Server 12 | :For FileMaker Server 12 | ||
:\FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\conf\Catalina\localhost\zulu.xml | :\FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\conf\Catalina\localhost\zulu.xml | ||
| − | + | ||
| + | Zulu will use this for any requests that come in without a username and password: this would let you use read-only .ics subscriptions in Google, for example. The section you want to modify specifies a jdbc.username and jdbc.password and looks like this: | ||
| + | |||
:<!-- jdbc.username and jdbc.password are the default values to try if the user does not supply any username or password. In most cases, these should be left to these (presumably wrong) values, so that the world will not have access to your calendar data. However, if you would like to allow non-authenticated requests to access the calendar without providing a username and password, enter credentials that correspond to a FileMaker account with whatever privilege set you want to grant. | :<!-- jdbc.username and jdbc.password are the default values to try if the user does not supply any username or password. In most cases, these should be left to these (presumably wrong) values, so that the world will not have access to your calendar data. However, if you would like to allow non-authenticated requests to access the calendar without providing a username and password, enter credentials that correspond to a FileMaker account with whatever privilege set you want to grant. | ||
:<Parameter name="jdbc.username" value="ReadOnly" override="false" /> | :<Parameter name="jdbc.username" value="ReadOnly" override="false" /> | ||
:<Parameter name="jdbc.password" value="insecure" override="false" /> | :<Parameter name="jdbc.password" value="insecure" override="false" /> | ||
| − | + | ||
| + | Replace the "value" portion of these last two lines, leaving the rest, including the override, intact. | ||
Revision as of 02:41, 22 April 2013
Read Only Calendars
iCal
You'll find a list of read-only versions of your calendar on the Publish page after you publish your file with Zulu (you can re-publish any time just to see these urls again if you forgot to copy them down).
To use this in iCal, copy (do not click) the subscription URL then move to iCal and select "Subscribe" from the calendar menu in iCal and enter the read only URL from the publish page.
Google Calendar
Google does not seem to like our .ics subscriptions: it doesn't know how to handle usernames and passwords when it comes to subscriptions. The best way to share out read only versions to Google is probably to use Google's sharing functionality. In this method, once you've successfully have all the calendars synced with your account, and even though you have read and write access, you can share these calendars to other Google accounts with read only permissions (click the "settings" link beneath your calendars in Google, the click "sharing" for any one calendar). This method works great, and only requires zulu to sync with one Google account.
Alternately, you can teach Zulu to use a default FileMaker account and password as specified below and this would let Google subscribe to Zulu .ics streams without entering an account and password. Using a default account and password for read only calendars.
You can enter a default user name and password in zulu.xml located here...
- For FileMaker Server 11
- \FileMaker Server\Web Publishing\publishing-engine\cwpe-tomcat\conf\Catalina\localhost\zulu.xml
- For FileMaker Server 12
- \FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\conf\Catalina\localhost\zulu.xml
Zulu will use this for any requests that come in without a username and password: this would let you use read-only .ics subscriptions in Google, for example. The section you want to modify specifies a jdbc.username and jdbc.password and looks like this:
