-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feedback Signicat/kpn on generated eHerkenning metadata.xml #4785
Comments
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 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
The text was updated successfully, but these errors were encountered: