[Tickets #14197] Re: Nag_Driver_Kolab stores parent_id strings base64 encoded (should be: unencoded)

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14197
------------------------------------------------------------------------------
  Ticket             | 14197
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Nag_Driver_Kolab stores parent_id strings base64
                     | encoded (should be: unencoded)
  Queue              | Kolab
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-12-29 15:27) wrote:


> The format of the Kolab UID's is not fixed and can contain ":" and
> other funky characters.
> I remember vaguely that's one of the reasons Jan changed the internal IDs
> when we reported that several backends were broken when using a Kolab driver
> + "special" UIDs that needed proper URI-encoding.

Wouldn't/shouldn't the xml parser/handler take care of the normal  
escaping for these characters, like it does for other string fields?

Either way, we can't use the internal ID of the task as the parent  
property. It MUST be the UID. If the regex isn't enough to catch the  
incorrectly set properties, maybe we can perform a look up of the UID  
to ensure it exists? That would be alot more expensive, so if we do  
need to do that, maybe we'd have to move this to a login task after  
all...

> @Jan: Do you remember anything about this?