A software vendor wants to extend their Outlook add-in so that the Outlook Calendar can be used to update the user’s Symphony presence.

The vendor will host the add-in on their site (or possibly a bank may host it as a valid add-in).

When a Symphony user installs the Outlook add-in, the add-in should be able to discover the identity of the Symphony user and use the On-Behalf-Off API to update the user’s presence status based on the user’s Outlook calendar.

I think this assumes that:

The user is running Outlook on their desktop
The user is running the Symphony Desktop UI on their desktop (is that required).

So the key issues are :

Can a windows desktop app discover the current Symphony user if either from some config file from the desktop app or from Cookies in the browser cache ?
If not the user can always enter their Symphony user id in a window prompted by the Outlook add-in.

In which case should we create a default component that can validate the user id.

How is the ‘add-in’ permissioned ? How does the user permission it? How does the ‘organisation’ permission it for their Pod?

Browser not supported