Duplicate attribute values in IdP 4.2

[Rod Widdowson]

> We're upgrading from 3.2.1 to 4.2.1. 

It sounds to me that you aren't upgrading but rather you installed a 4.2.1 IdP and threw the 3.2.1 configurations at it.   An upgrade would be to just install 4.2.1 over the 3.2.1 installation (or even a copy of it).  To do a new install you would need to make changes to the distributed configuration to match your requirements.  You are falling between the two options - which is the hardest of all three.

The development team put a lot of effort into making upgrades work - precisely so that behavior such as you have observed doesn't happen.

> So presumably this is the cause. We hadn't yet configured any AttributeRegistry, but it looks like that is the way forward?

Well, once you have upgraded you can consider the new configuration possibilities (and an explicit AttibuteRegistry is part of that) and move forward.  But the key point is that you can move from old-style configuration to new-style at your own speed - you don't have to "big bang" configuration and IdP version (and container) in one go..  By doing an upgrade you get to take advantage of bug fixes immediately then you can streamline your configuration at your leisure.

Rod