Support single care organization multiple vendor scenario

[woutslakhorst]

Some care organizations select their software based on a best-of-breed scenario. For some bolts this can mean that part of the process is supported by vendor A and part is supported by vendor B. For security reasons, both vendors will register the care organization under different DIDs. This will:

• confuse the authorizing party, since multiple care organization entries exist.
• result in multiple NutsAuthorizationCredentials, one for each vendor.
• result in vendors "hacking" custom solutions for a bolt.

[woutslakhorst]

This is almost impossible without a valid third party credential issuer (LRZA).
for eOverdracht this might possibly be resolved with one party acting as proxy.