Open sjoerdie opened 1 year ago
Initial assessment: Sounds like a bug indeed but we still need to figure out how we can use eIDAS for anything useful if we don't get the BSN or KvK-number.
requested by: RID 82 + 143
Aanvulling vanuit NOP 104:
Scoping regels t.b.v. AuthnRequest in de preproductie omgeving
<samlp:Scoping xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:IDPList xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:IDPEntry xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
ProviderID="urn:etoegang:EB:00000004000000149000:entities:9009"/>
</samlp:IDPList>
</samlp:Scoping>
Scoping regels t.b.v. AuthnRequest in de productie omgeving:
<samlp:Scoping xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:IDPList xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
<samlp:IDPEntry xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
ProviderID="urn:etoegang:EB:00000004000000149000:entities:0001"/>
</samlp:IDPList>
</samlp:Scoping>
Product versie / Product version
2.0.0
Omschrijf het probleem / Describe the bug
https://developer.signicat.com/broker/knowledgebase/changes-to-idp-scoping-in-signicat-identity-broker.html#eherkenning
eIDAS testen is nu niet meer mogelijk.
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
Screen resolution
No response
Device
No response
OS
No response
Browser
No response