Dan Posted July 13, 2006 Report Share Posted July 13, 2006 We are attempting to work with the "Publish Secure Calendars" ... some advanced coding ... not made much progress (and not spent much time trying). BUT, would still prefer a more simple link that could embed a simple password to a published calendar. Seems that if the password could be passed in an RSS feed URL, the URL for any calendar/spud could also provide a password. Quote Link to comment Share on other sites More sharing options...
Jill Posted July 19, 2006 Report Share Posted July 19, 2006 You can create a URL that encrypts the URL for your calendar but is more static. It is a little involved, but in my opinion once you get it it's not as overwhelming as the sample code. First, because you'll still encrypt the URL for your calendar, you'll need to use an online MD5 encryption tool. We used a couple of different ones: iWebTools and B-Con, which we found with a basic web search. Both worked fine. Just go to one of those sites and keep that browser window open while you create the URL. To create the secure URL: In a second browser window or tab, display your published calendar, click Publish, and go to step 4 of the wizard. For Access type, select Secure URL, set your password, display the secure key, and then select and copy it. Click Done to publish the calendar with this new secret key. Open the web page where you embed your calendar. In the script that displays the calendar, for the src attribute, enter the following:https://www.trumba.com/k.aspx?calendar=calendarwebname&expires=201012312359&hash=securekey replacing the text in blue with your calendar web name and the secret key you copied. You can also change the expiration date to the one you want. In the URL, select all of the text that appears after the question mark (starting with "calendar=" all the way to the end of the secret key). Go to the browser window or tab that is displaying the MD5 conversion tool, paste the string you copied into the text side, and click Encrypt or the equivalent command if there is one. Select the new encrypted string, go back to your web page, and in the URL, for hash=, delete the secret key and paste your new encrypted string. Save your web page and test it by viewing it in a browser. The calendar should appear without prompting you for a password. But remember that because the hash parameter is static, the URL isn't as secure as it would be if you used the sample code. But it's a slightly more secure way of doing it than passing the unencrypted password, and more importantly, it's something we can do right now. Quote Link to comment Share on other sites More sharing options...
Dan Posted July 19, 2006 Author Report Share Posted July 19, 2006 Appreciate the simplified steps ... we'll let you know. And, actually, it is not rocket science we are protecting ... an unsecure password passed in the URL really would be adequate. The alternative we were about to implement (and be satisfied with) was to make a simple passworded calendar and have users manually enter it each time. By passing the password in the URL, it is slightly more secure in that we do not need to document what it is anywhere and could make it quite extensive. Quote Link to comment Share on other sites More sharing options...
Jill Posted July 20, 2006 Report Share Posted July 20, 2006 Please do keep us posted. Yes, these alternative steps work for spuds as well. In the URL, after the hash parameter, you'd add &widget=[spud name]. And you can get the spud name in the code at the end of the publishing process. So, for example, if you wanted to add the Date Finder spud, and your calendar web name is kexp, the src attribute in your script tag would look something like this: src="<https://www.trumba.com/k.aspx?calendar=kexp&expires=201012312359&hash=[encrypted stuff]&widget=datefinder" Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.