Given the attached security manager plugin schema, I'm experiencing unexpected behavior when defining instances of the ConfigUser element.
The attributes are defined with order: user, password, addresses, status, nvps
The attributes are presented with order: addresses, nvps, password, status, user
I can create and populate multiple instances if I enter the attributes in this order: addresses, user, status, nvps, password
Attempts to populate instance attributes in other orders (e.g., user, status, password, nvps, addresses; or addresses, nvps, password, status, user) causes an exception (“-1: No such component in environment: 'AccurintSecurity' named 'accurintsecmgr'.”) to be thrown when setting some of the attributes. The order of entry appears to affect which attributes generate the exception for a single instance, with some orders allowing four attributes to be entered before failing on the fifth while others fail sooner.
I don't know if this is a bug in the platform, or my schema. I have not observed this behavior with siblings of ConfigUser. I have reproduced the behavior with a seemingly clean install of the platform and plugin, making changes to the default environment.xml file.
This behavior was observed previously and attributed to tooltip content attached to the nvps attribute. Removal of the tooltip seemed to fix the problem, but I've since observed the order of entry changing the behavior.