From e8e274c9e0a9fb9d2ef775f99c763d97b23050b1 Mon Sep 17 00:00:00 2001 From: Rob Crittenden Date: Wed, 8 Dec 2010 13:26:27 -0500 Subject: Properly handle multi-valued attributes when using setattr/addattr. The problem was that the normalizer was returning each value as a tuple which we were then appending to a list, so it looked like [(u'value1',), (u'value2',),...]. If there was a single value we could end up adding a tuple to a list which would fail. Additionally python-ldap doesn't like lists of lists so it was failing later in the process as well. I've added some simple tests for setattr and addattr. ticket 565 --- tests/test_xmlrpc/objectclasses.py | 1 - 1 file changed, 1 deletion(-) (limited to 'tests/test_xmlrpc/objectclasses.py') diff --git a/tests/test_xmlrpc/objectclasses.py b/tests/test_xmlrpc/objectclasses.py index 54c8c280..5f230b43 100644 --- a/tests/test_xmlrpc/objectclasses.py +++ b/tests/test_xmlrpc/objectclasses.py @@ -30,7 +30,6 @@ user = [ u'posixaccount', u'krbprincipalaux', u'krbticketpolicyaux', - u'radiusprofile', u'ipaobject', ] -- cgit