Calendar Synch Problems in Luminis IV

0
No votes yet

Bad news... The way the immutable identifier has been implemented in Luminis IV causes a predictable problem when doing Outlook/PDA desktop synchronization with Sun Calendar. The sync tool no longer expects a uid/password combo, but rather an immutable id/password combo. I'm sharing this explanation, plus further detail from support so you may avoid hours of investigation and back and forths with support, as well as take the necessary acts on campus to account for this.

From support:

Unfortunately the issue at hand is as designed. The SunJavaCommSync.exe is hard coded to look for uid=. That being said the immutable id can be configured in a variety of different ways. These are outlined in the attached admin guide, beginning on page 233. But once configured cannot be change.
Platform IV provides the ability to change the login identifier of a Platform user account after initial account creation, but not the immutable id. The immutable identifier is treated as a surrogate key for the account. In addition to the core ability to change the login identifier for a user account, several other pieces of functionality were also introduced:

Ability for a user account to be associated with multiple login identifiers -- a primary login identifier and zero or more login aliases. This functionality is useful if a transition period is needed when both the old and new login identifiers are valid.

Ability to share the account immutable identifier with integrated systems in addition or in place of the login identifier.

Ability for an account to be associated with multiple e-mail addresses -- a primary address and zero or more aliases.
I can see how asking users to remember the immutable id is problematic, but this id can be configured to be in a more user friendly form. As outlined in the admin guide.

Highly annoying... I wish they could have created some sort of shim software that listened on port 6785 and remapped uid to immutable id as an inbetween service for the sync process. Alas they did not...

In the short term, we are going to create a way in the portal for users to look up their immutable id for this purpose. In addition, we will have to write up detailed docs on how to change their sync settings. For us this will be the final straw on campus for eliminating Sun calendar.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Calendar Sync Problems Luminis 4

Just curious if you have been successful to sync calendars in Luminis 4? We just went live with Luminis 4 in production this week, I have just downloaded the new Sun java System Communications app and was hoping you had some advise::)

What port is the connection to the Communications Express Server for the Address Book running on? I assume the Calendar is still on 6785.

Thanks,

Sara Huntley
Luminis System Admin
University of North Alabama

Thanks for your post.

I would agree that the immutable ID is quite a departure from what we are familiar. It has caused us some problems in that we have been pursuing a OTA wireless sync package that has not worked as it normally would with Sun Calendar One. Your dialog did give me some ideas to try with respect to including the immutable ID as the login name. This coupled with the password may actually work with the OTA system. If you are intersted, I will enter another post when I know if I am successful.

John Stanton
Director, Customer Service & Training
UAH Computer & Network Services