On Tue, Apr 07, 2015 at 09:23:57PM -0500, Endi Sukma Dewata wrote:
On 4/7/2015 7:30 PM, Fraser Tweedale wrote:
>>>>1. Since the profileId and classId are virtual properties and have their
own
>>>>LDAP attributes, they should not be stored in certProfileConfig
attribute
>>>>when a profile is added/modified.
>>>>
>>>Done. Because the profile configStore is written and read directly
>>>by the ProfileService, the solution to achieve this is also in that
>>>class.
>>
>>I think the classId provided during createProfileRaw() and
>>modifyProfileRaw() should be stored in both mProfileClassIds Hashtable and
>>in classId LDAP attribute.
>>
>The classId gets stored in mProfileClassIds, and in the LDAP
>attribute, by the createProfile() method.
I think I tried changing the classId using the ca-profile-edit command and
it didn't get changed in the LDAP entry. Could you verify this? If it works
that's good. If it doesn't, let's fix this in another patch. Thanks.
Ah, yes. The classId is never changed, I this this was the existing
behaviour. I'll confirm and if so, I'll file a ticket.
Cheers,
Fraser
--
Endi S. Dewata