The current prefill plugin has insufficient WS-Security and WS-Addressing.
WS-Security missing multiple choices of key type identifier such as "BinarySecuritytoken" and "X509SubjectKeyIndentifier", so the message is not correctly signed.
WS-Addressing is missing a "wsa:from" with required OIN and the current "wsa:to" also required OIN but as workaround it can be set in de Suwinet bindings.
See documentation from inlichtingenbureau for connection and message/payload data:
Besproken met Susanne, Leeuwarden staat er voor open om deze wijziging met assistentie vanuit Maykin zelf te realiseren, met als voorwaarde dat zij verantwoordelijk zijn tot aan acceptatie van de wijziging
Product versie / Product version
2.7.10
Customer reference
Taiga Leeuwarden 29
Gemeente Leeuwarden and others
Omschrijf het probleem / Describe the bug
The current prefill plugin has insufficient WS-Security and WS-Addressing. WS-Security missing multiple choices of key type identifier such as "BinarySecuritytoken" and "X509SubjectKeyIndentifier", so the message is not correctly signed. WS-Addressing is missing a "wsa:from" with required OIN and the current "wsa:to" also required OIN but as workaround it can be set in de Suwinet bindings.
See documentation from inlichtingenbureau for connection and message/payload data:
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response