Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Remove configuration property to disable new API elements
|
|
Reason: some elements are 'date' now, but was defined as 'date-time'
|
|
"Meldegesetznovelle 2023)
|
|
"Meldegesetznovelle 2023)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Inlcude Spring 5.3.26 to fix CVE-2023-20859, CVE-2023-20861, CVE-2023-20860
|
|
|
|
|
|
|
|
|
|
Reason: special characters are requiered in plain text
|
|
|
|
ERnP does not support partial personData updates.
Therefore, we have to copy the latest ERnP result to all information during
an update request.
|
|
|
|
|
|
|
|
|
|
|
|
- not-notified LoA is currently used by Ukraine
|
|
Since Ukraine is not notified, we need a new configuration parameter to set not-notified LoA
|
|
to IDA EntityId
Reason: EntityId is the default configuration property
|
|
|
|
|
|
|
|
|
|
|
|
prohibited by matching-process
|
|
matching-result
That flag disable a new ERnP entry by user decision
|
|
- filter all entries that are marked as "PersonAmtlichBeenden"
- set flag 'allowNewErnpEntryByUser' to false in case of matching steps that requires single hit
|
|
and more than one ERnP results
ERnP responses can include more than one results that are a mix of active and
in-active persons. Therefore, we have to clear fist and check uniqueness afterwards
|
|
eIDAS Node
|
|
Reason: The IDA Shibboleth IDP does not support PERSISTENT yet
|
|
|
|
|
|
|
|
|
|
GrayLog connections
|
|
countries
|
|
|
|
|
|
|
|
and automated
|