[OPENAM-7124] Having an invalid COT name in the metadata causes a large number of providers to disappear from the COT upon deletion. Created: 15/Oct/15 Updated: 01/Oct/18 Resolved: 12/Dec/16
|Affects Version/s:||12.0.1, 12.0.2|
|Fix Version/s:||12.0.5, 13.5.1, 14.0.0|
|Reporter:||Tina Roper||Assignee:||Mark de Reeper|
|Sprint:||AM Sustaining Sprint 14, AM Sustaining Sprint 15, AM Sustaining Sprint 21, AM Sustaining Sprint 32|
|Support Ticket IDs:|
When an entity provider is imported into the console with an invalid COT value in the extended metadata, it will cause problems when trying to delete it. After you have deleted the provider from the entity provider list, the provider will still be in the COT. Navigating to the COT page and trying to remove the entity from the COT list will cause an error "Input entity id is invalid" resulting in the user needing to hit the back button in the console. Once back on the federation page, over half the providers that were in the COT are now removed from the list.
Steps to create:
1. You will need a large number of metadata files in one circle of trust, I had 35.
At this point the entity will be in the COT successfully.
6. Delete the provider from the entity provider list, which should remove it from the COT but does not.
|Comment by Mark de Reeper [ 04/Nov/15 ]|
Using the test metadata data from the AAF (contains over 300 entries) and an initial run through on a recent 13 trunk build and I was not able to reproduce the final step, 9. After hitting Back button in the console there were no observed entries missing from the COT list but did see the error in step 7.
Will try to reproduce on a 12.0.1 build next.
|Comment by Mark de Reeper [ 05/Nov/15 ]|
No luck with 12.0.1 either, can see that improvements could be made to the COT validation during import as currently the value in the extended metadata is not taken into account.
|Comment by David Bate [ 09/Dec/15 ]|
This issue was reproduced with XUI turned off, so may only occur in the Legacy UI.
|Comment by Hunter Poe [X] (Inactive) [ 12/Jan/16 ]|
We experienced a very similar error when we brought an entity into a CoT through the legacy UI console, and then deleted it prior to removing it from the CoT which resulted in the "Input entity id is invalid" error appearing in the console and then most of our CoT disappeared. We are using OpenAM 12.0.2
|Comment by Abel Hoxeng [ 27/Jan/16 ]|
I was able to reproduce with the following steps:
1. Export an entity's metadata and extended metadata.
To fix this issue I did the following:
1. Edit the Metadata for the correct COT
|Comment by Filip Kubáň [X] (Inactive) [ 28/Apr/17 ]|
Verified on OpenAM 13.5.1-RC2 Build 149fc42dac (2017-April-20 08:29)