Hi @Tobias_Moritz !
I will start with the bottom line - the key for success will be:
Once the PDP/PEP finished the JHF upgrade - clear it's tables. If it's cluster, clear all members at once.
There is no breaking change between PDP to PEP sharing in this bundle.
And for the long version:
In Identity Awareness R&D, we have done an internal quality cycle on Identity Sharing flows, to raise issues proactively.
As part of this cycle, we have created more than 20 code changes which are both functional, optimization and debuggability improvements.
This bundle was already implemented with some key customers production and in large QA cycle to ensure high quality before adding to the JHF.
If the IDA tables will not be cleared, 2 main behaviors are possible:
1. leftovers on the kernel tables, which usually not cause any issue other than memory taken by them.
2. temporary sync issues to PEP in Identity Sharing, until the next sharing sync.
Since upgrading JHF anyhow involves maintenance window, I prefer writing the above SK to avoid such undesired behaviors.
If you have any additional questions, feel free to tag me 😊
Thanks,
Royi Priov
R&D Group manager, Infinity Identity