[ngw] Restricting Access to Calendar Publisher

Joseph Marton jmmarton at gmail.com
Mon Sep 2 23:49:49 UTC 2013


Looking at this a different way... what if the users added a second
ActiveSync account, pointing to the central calendar user account?  That
would allow them to see and post to the calendar without having to use
Calender Publishing.

Joe


On Mon, Sep 2, 2013 at 3:09 PM, Matt Weisberg <matt at weisberg.net> wrote:

>
> I have a customer that has used GroupWise for a long time, since 4.1 days.
>  They have some unique ways of using GroupWise.  One is that they have a
> certain mailbox that all the users have proxy rights too.  The users post
> common scheduling data on the calendar for this account, called central.
>  This is a small law firm.  So for example, the attorneys will put when
> they have hearings on this common calendar.  They'll proxy intro "central"
> and put items on the calendar.  They also use this to indicate when they
> are out, holidays, major office events, etc.  So it provide s common one
> screen view of everyones schedule for the most part.  They've done this for
> many years, as far back as I can remember.
>
> So now in the last few years they all have phones and use ActiveSync
> through the GroupWise DataSync server to get mail (most don't seem to use
> their personal GroupWise calendar).  But one problem they have is that they
> cannot easily see central's calendar on their phones.  Sure they could
> login to WebAccess, proxy over, and look at the calendar, but that is
> cumbersome at best, and very difficult on a phone.  So I thought, why not
> use Calendar Publisher.
>
> The problem with Calendar publisher is that there is no security on it.
>  It is basically public and if you know the URL to get to a public
> calendar, you can view it all.  The central calendar has some data that
> probably should not be public.
>
> So what I did was I took NetIQ Access Manager and put Calendar Publisher
> BEHIND it.  Access Manager provides the security front-end, requiring
> authentication, so that only the customer's users can reach it.  I had to
> use the non-redirected login method with AM, but it works just fine.
>
> I test it with iOS devices, adding a calendar account, and it works
> perfectly.  The calendar syncs right into the iOS calendar and iOS stores
> the user's credentials in the calendar account.  Works perfect.  I also
> tested it with Apple's iCal on my Macbook, and that works perfectly too.
>  But I have one problem: Android.
>
> I have yet to figure out how to get a protected calendar like this to sync
> to Android.  From what little I've found on it, there is no way to do it
> directly from an Android device.  I'm using a Nexus 7 to test.  You cannot
> subscribe to calendars from the device itself.  Everything I read says you
> have to go into your synced Google Account and add/subscribe to a calendar
> there.
>
> So ok, I tried that, but even in there, I cannot add credentials. When you
> add a calendar you want to subscribe to, you add the URL but there is no
> where to put credentials (at least no where that I found).  Am I missing
> something here?  I'll admit I'm more of an iOS guy, but I figure there must
> be a way to do this on Android, right?
>
> Anyway, this is a great solution to secure Calendar Publisher (a major
> missing feature in Calendar Publisher IMHO).  And Access Manager is fairly
> inexpensive in small user counts, so even smaller customers could benefit
> (guess I should maybe do a cool solution on it).
>
> So can any Android experts help me out?  This customer I did this for does
> have both, so I don't want to leave the Android users out in the cold on
> this.  Thanks.
>
>
> Matt
>
>
> --------
> Matt Weisberg
> Weisberg Consulting, Inc.
> matt at weisberg.net
> www.weisberg.net
> ofc. 248.685.1970
> cell 248.705.1950
> fax 248.769.5963
>
> _______________________________________________
> ngw mailing list
> ngw at ngwlist.com
> http://ngwlist.com/mailman/listinfo/ngw
>


More information about the ngw mailing list