Bugzilla – Bug 671803
iManager fails to properly set Grace Logins Allowed when modifying multiple objects.
Last modified: 2018-10-30 06:54:52 UTC
Created attachment 413908 [details] Screenshot showing how the failed change was attempted from iManager. iManager 2.7.4 eDir Plugins (in case they matter): 2.7.20100818 A customer has reported that when trying to modify multiple objects (users) to set their grace login information at the same time that the update does not take place properly on the destination objects. Instead of replacing the values in the Counter attribute it simply pushes the new value which, in all cases, causes the counter to increase its resulting value (because, in this case, iManager only allows positive integers to be added). The result is that in order to modify these values the customer must do them all individually or fall back to other tools like using LDAP which defeats the purpose of our management console. Below is a user that I modified using the multiple-object modification functionality of iManager. At first they had 15 grace logins remaining (I'd already done a couple tests) and when I (as shown in the attached screenshot) changed their grace login limit and grace logins remaining values to '1' (set to replace both of those values) the limit changed to '1' (it's an integer attribute) but the counter increased to 16. This is reproduced 100% of the time in my testing. # testDummy00, novell, org dn: cn=testDummy00,o=novell,dc=org logingracelimit: 15 logingraceremaining: 15 # testDummy00, novell, org dn: cn=testDummy00,o=novell,dc=org logingracelimit: 1 logingraceremaining: 16 Expected Results: 'Replace' should actually replace values, not cause addition to take place, regardless of the attribute type. Actual Results: Counter attributes in general (I assume) are not replaced but instead are added-to. This feels like an error in iManager as a whole.
Additional information: Confirmed On iManager v2.7.3 (20090916_090939) the attempt to change grace logins remaining for multiple users would result in a name space exception com.novell.admin.ns.NamespaceException: SINGLE_VALUED_ATTRIBUTE at com.novell.admin.ns.NamespaceException.(NamespaceException.java:67) at com.novell.admin.ns.ObjectAttribute.addComponent(ObjectAttribute.java:298) at com.novell.emframe.dev.DataHandlerHelper.writeToMoo(DataHandlerHelper.java:858) at com.novell.emframe.dev.DataHandlerHelper.setString(DataHandlerHelper.java:306) at com.novell.emframe.dev.DirUtils.writeAttributeXML(DirUtils.java:928) at When creating a custom plugin to change grace logins remaining with PluginStudio, the options Ignore/replace/add/remove will be displayed, but choosing "replace" results in the same name space exception.
Hi Aaron , I am trying to duplicate this defect in my test box , but i couldn't hit this issue. Could you please provide the machine access details .So , that i can reproduce this issue locally . As mention in comment #1 , that defect is fixed as part of iManager274 (defect # 597690). Thanks Anil
As mentioned my modify was done with 2.7.4 so either the other problem is not fixed or else this is separate (more likely) based on the schema. What steps did you try? This is, as mentioned before, 100% reproducible in my testing regardless of iManager or tree.
Created attachment 685847 [details] Screenshot showing issue This problem is still occurring in OES. There is no dialogue box to be able to set/unset Limit Grace Logins. (I also note that the same is true of Force Periodic Password Changes.
Customer: Surrey County Council SR Number: 101017556579 Bug Number: 671803 Issue Type: [0] Normal Severity: [-100] Normal Entitlement Type: [-250] PSE Workaround: [-10] Yes-But not acceptable to customer Environment: [-20] Production Frequency: [-65] Continuously # of Users Affected: [-75] 1000+ Potential Users: [-20] 1000+ DSLA Required: true NTS Defect Priority: 460
This was originally found in 2.7 SP4, so setting the Version back accordingly.