Showtime
My Blackberry Enterprise Server Push Utility for the Lotus Notes Client, allows you to create Jobs for individual Channel, Message, and Browser Content Pushes, as well as allows you to delete Pushed Channel Icons from defined recipient devices.
Contact Information
Blogger, podcaster, writer, and geek Chris Toohey covers topics from application development to the latest must-have-gadgets.
dominoGuru.com on Facebook
Latest Updates
Products & Applications
Time Tracker
The idea is simple. At the start of your day - upon completion of your first task - create an entry highlighting what you did and whether you feel it was an efficient or inefficient use of your time. Based on several requests, you can also select the priority, apply categories, or even align your time against a project.
For Lotus Notes Client v8.0 and above, you can use the Time Tracker Widget to make this process even easier!
Zephyr
My Configuration-based Rich Text Mail Merge and Emailing Utility, Zephyr allows you to create rich, data-driven emails to support automated workflow - all via Microsoft Word Mail Merge-like architecture. Dear <firstname> allows you to personalize each email message not only to the individual recipient, but also to the individual application workflow event!
xCopy
xCopy is a simple configurable xCopy client for the Lotus Notes client. By creating and defining xCopy Profiles, you can batch process your file backup or remote upload jobs. With the addition of the xCopy sidebar widget, you can easily kick-off these jobs, and modify both the xCopy Profiles and xCopy itself.
Community & Resources
Lotus Technical Information & Education Community
The Lotus Technical Information & Education community is comprised of IBM, business partner, and customer subject matter experts who use product wikis, published articles, white papers, community blogs and the latest in social media to build and share high quality technical content.
OpenNTF.org - Open Source Community for Lotus Notes Domino
OpenNTF is devoted to enabling groups of individuals all over the world to collaborate on IBM Lotus Notes/Domino applications and release them as open source.
developerWorks Lotus : Wikis
Share your deployment experiences and best practices in our wikis and help IBM to create scenarios for successful deployments. Contribute to the community by collaborating on shared content and leverage the shared knowledge from that community.
Creating Oauth-like MD2 Hash Keys for IBM Lotus Notes Domino Web Applications
01/25/2010 12:15:35 AM by Chris Toohey
Since my drivetime thoughts on mobile device authentication to SOTU -- my Remote Console Command Utility for IBM Lotus Notes Domino -- I've been giving the architecture some serious thought. I think, at this time, I've got it! To recap, I don't want each of the mobile devices to require authentication per se to SOTU, but rather create an Oauth-like, MD2 Hash Key that a Lotus Notes Domino Administrator could enter into their device. The more I think about it, the more excited I am to see this in practice... so while this write-up discusses the overall idea and keeps to architecture, be certain that I'll have a proof of concept of this technique hopefully as quickly as early this week.
As I am a firm believer in that old adage about pictures, so I thought the easiest way for me to explain the concept would be to give you a visual representation of the overall architecture of it:
SOTU sits on our Domino Server. A local client -- represented by the laptop in the above diagram -- authenticates either via Lotus Domino HTTP Authentication or Lotus Notes Client Authentication. Basically, we're just going to confirm that the authenticating party is who they purport they are... and once that's confirmed, we're going to do two things:
- A key profile will be generated, tracking who made the request, and marry the requester with their randomly-generated MD2 Hashed Key.
- Return the same MD2 Hash Key to the requestor, for use in their mobile devices.
(The more I think about it, I should simply create the whole thing from the mobile device client UX - an initial mobile device client browser authentication to the Lotus Domino HTTP server and there's no hassle.)
The requester can now share that MD2 Hash Key with any number of their devices (which have the SOTU mobile client installed, of course).
Now, that part is easy... and so is the next quite frankly.
Each and every HTTP Request that is submitted to SOTU is non-authenticated. Anonymous FTW! See, unless you supply a valid MD2 Hash Key as part of the HTTP Request, nothing happens. Without that key, the request is ignored!
To pull this off, ideally you'll want SOTU to have an HTTP Request Consumer Proxy to... well, quite frankly consume the HTTP Request and proxy that request (once we have a valid, active Key) to SOTU.
Like I said, easy.
This approach gives you the added bonus of being able to kill a given user's access to the system by killing the Key!
So... thoughts on this approach? Like I mentioned the other day, I'm going to keep this whole process pretty open and out there, so feedback rocks. Think this will work, or blow up in my face, or couldn't care less either way? Let me know via the comments on this post!
Tomorrow (when I wake up), I'll get started with the aforementioned proof of concept and test my theories!
|
Unless otherwise stated, this work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License. |