Open LaurensBurger opened 1 month ago
Ik begrijp niet waarom we optionele attributen moeten weglaten...
Optional attributes can stay because KPN might need them (just a guess - we added them sometime for a reason).
Can someone check where that attribute kvk does need to be?
feedback from KPN regarding KVKnr
<md:RequestedAttribute Name="urn:etoegang:1.9:EntityConcernedID:KvKnr" isRequired="true"/> deze regel Verwijderen, het betreft hier een zogenaamd ‘identificerend kenmerk’ dat via het onboardingsformulier wordt opgenomen in de Diensten Catalogus van het stelsel.
they suggest the following which can be done form the admin already:
<md:RequestedAttribute Name="urn:etoegang:1.9:attribute:FirstName" isRequired="true" />
<md:RequestedAttribute Name="urn:etoegang:1.9:attribute:FamilyNameInfix"
isRequired="true" />
<md:RequestedAttribute Name="urn:etoegang:1.9:attribute:FamilyName" isRequired="true" />
<md:RequestedAttribute Name="urn:etoegang:1.9:attribute:DateOfBirth" isRequired="true" />
but, we don't use these attributes from the digid/eherkenning login, all we need is BSN/KVKNr and then we look up these details via prefill plugins.
Perhaps these suggestions were meant only for the eIDAS?
Thema / Theme
Admin
Omschrijving / Description
kpn:
Signicat:
Added value / Toegevoegde waarde
No response
Aanvullende opmerkingen / Additional context
No response