- UNIFYBroker Forum
-
Bugs
UNIFYAssure-Aurion-Sample install reports that field names are reserved after restart
I just restarted my Broker instance (to try to clear a Link baseline sync that appeared unwilling to stop) and now I see this error in the dashboard. My install is a UNIFYAssure-Aurion-Sample with few changes other than a 'Request Schema' from AD and addition of a handful of other fields in Links and Lockers.
What should I do about it?
Answer
This appears to have started since I did the Request Schema on the AD connector.
I've removed those fields from the connector and it looks better now but I'm still not sure why they were added for me.
OK to close this ticket if you want to, although it's not great that this is the default behaviour after a 'Request Schema' on the AD connector.
It's the field name in AD, what would you like it to do instead?
My suggestion is that the Request Schema UI unticks the tick boxes next to the fields which are reserved by the LDAP specification by default.
If the tick boxes are subsequently turned on by the user then another confirmation dialog could inform the user that this problem is going to occur on their Adapter. At least they've been forewarned then :-)
Hey Adrian,
Thanks for the suggestion. At this time, after some discussion we've concluded that it would potentially confuse people more if the connector schema was to automatically un-tick the box next to fields reserved by the LDAP specification.
The reason for this, is that it's perfectly acceptable to have these fields in the connector schema, and they will only be an issue when subsequently exposed on the adapter. However, it is a normal use case for a connector to not be exposed to an adapter directly; rather to be joined and aggregated on an existing adapter. In this case, the reserved field names would not be exposed down to the gateway so wouldn't cause any problems.
Customer support service by UserEcho
Hey Adrian,
Thanks for the suggestion. At this time, after some discussion we've concluded that it would potentially confuse people more if the connector schema was to automatically un-tick the box next to fields reserved by the LDAP specification.
The reason for this, is that it's perfectly acceptable to have these fields in the connector schema, and they will only be an issue when subsequently exposed on the adapter. However, it is a normal use case for a connector to not be exposed to an adapter directly; rather to be joined and aggregated on an existing adapter. In this case, the reserved field names would not be exposed down to the gateway so wouldn't cause any problems.