Under review

Duplicate Adapter IDs in extensibility clear the extensibility file on failed service start

Hayden Gray 2 years ago in UNIFYBroker Service updated by Matthew Davis (Technical Product Manager) 2 years ago 1

Hello Team,

I understand editing the service extensibility config directly is not supported/recommend, and therefor this issue shouldn't be expected to impact any environments under normal circumstances. However I found some interesting behaviour that occurs when an AdapterConfiguration object in the Unify.Product.IdentityBroker.AdapterEnginePlugInKey.extensibility.config.xml file is given a duplicate "AdapterId".

When attempting to start the service with an incorrect configuration like this, the service fails to start which is expected, however the entire Unify.Product.IdentityBroker.AdapterEnginePlugInKey.extensibility.config.xml file is also cleared and saved in the process. Clearing any other configuration that may be there. I'm unsure if this is intended behaviour, but figured I would log this here anyway for your consideration so the service would simply fail and not save over the configuration.

UNIFYBroker version 5.3.1


Under review

Hey Hayden,

Thanks for opening this one for us. We'll definitely look into this one - I think what you've described is perfectly expected. It should fail to start, but shouldn't be overriding the configuration in the process. We'll take a look at this one and see what's going on - I'll leave this bug open for now so we can track any fix we do implement.