[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Photos in the 7.1.x GAL



Resync the full gal should be:
fullSync [-a {galsynceaccountname}|-i {account-id}] [-d {datasource-id}] [-n {datsource-name}]

- Raja


From: "Raja Rao" <raja.rao@zimbra.com>
To: "Rich Graves" <rgraves@carleton.edu>
Cc: zimbra-hied-admins@sfu.ca, "Thom O'Connor" <thom@zimbra.com>
Sent: Thursday, August 4, 2011 10:57:21 AM
Subject: Re: Photos in the 7.1.x GAL

Hi,
We have filed a bug http://bugzilla.zimbra.com/show_bug.cgi?id=62966 to look into this. But, if you have photo name in LDAP(option# 3), you are half way there. People search depends on two variables:  "photoFileName" and "photoUrl". 
photoFileName - is the LDAP property name that contains the name of the photo. Like: "raja.jpg"
photoUrl - is the actual url to get that photo. This variable is actually used w/ in Zimbra web client. 

1. To get photoFileName from LDAP to webclient(when webclient does GAL search):

zmprov mcf +zimbraGalLdapAttrMap extensionAttribute1=photoFileName +zimbraGalLdapAttrMap ou=department

Resync the full gal:
zmgsautil fullSync -a galsync@zimbra.com -n vmware.com

2. Once the GALSearch is returning the information back to the client, we need to construct photoUrl.
When a people-search is done, web client calls a Zimlet and passes photoFileName. This Zimlet will construct photoUrl and return for each item. This will be addressed by bug 62966. This will be generic Zimlet and you will set URI info for your university.


PS: If you have entire photo url itself in LDAP, then you don't need any Zimlet, but then you can configure step1 to directly return photoUrl.
 

- Raja


From: "Rich Graves" <rgraves@carleton.edu>
To: zimbra-hied-admins@sfu.ca
Sent: Thursday, August 4, 2011 8:52:57 AM
Subject: Photos in the 7.1.x GAL

I feel I need to do something positive to justify the space-wasting "People Search" box.

I can see several ways to get better campus directory integration:

1) Overload the whole thing with a zimlet and/or skin

2) Hack at the jsp's, or something, to overload just the photo call (we are fairly liberal with photos, basically referer+campus source ip address is enough to get pictures of anyone but students with FERPA directory opt-outs)

3) Use Zimbra's GAL sync to get our existing jpegPhoto's into Zimbra. This appears to be impossible right now.

4) Stop scheduled GAL syncs. Run zmgsautil forceSync, immediately followed by a non-Zimbra script to suck jpegPhoto's out of our LDAP and shove them into the galsync account.

#4 looks most promising to me. Has anyone else been down one of these roads, with code and war stories to share?
--
Rich Graves http://claimid.com/rcgraves
Carleton.edu Sr UNIX and Security Admin
CMC135: 507-222-7079 Cell: 952-292-6529