Currently type conversion of parameters and attributes is done ad-hoc in many places in the code. It is often hard to find where a particular parameter or attribute value is converted and one can't be sure what Python type is the value using at any place in the code. The code is error-prone and hard to maintain and bugs in the code often have to be fixed by hacks (#1259, #2039, #2025, etc.)
Change the way parameter and attribute values are decoded/encoded in IPA, so that the parameter-specific Python type is always used for the values. Let border backends (xmlclient, Executioner subclasses, ldap2) handle decoding and encoding of values in a backend-specific way.
See http://www.redhat.com/archives/freeipa-devel/2012-January/msg00075.html for more information.
Related to https://bugzilla.redhat.com/show_bug.cgi?id=870446
Replying to [comment:10 dpal]:
This ticket should supersede and remove temporary solution implemented as a part of ticket #3220 (see patch there).
3.4 development was shifted by one month, moving tickets to reflect reality better.
Adjusting time plan - 3.4 development was postponed as we focused on 3.3.x testing and stabilization.
Moving unfinished November tickets to January.
The FreeIPA 4.2 was already shaped (see [[milestone:FreeIPA 4.2]] milestone), this does not fit. Pushing out.
If anyone is willing to help and contribute to this one, please let us know!
Metadata Update from @jcholast: - Issue assigned to jcholast - Issue set to the milestone: FreeIPA 4.5 backlog
Login to comment on this ticket.