Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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
|
|
into nightlybuild
|
|
|
|
|
|
|
|
error-case too
|
|
|
|
|
|
and automated
|
|
|
|
|
|
|
|
|
|
by user decision
|
|
include commons-text-1.10.0 to fix CVE-2022-42889
|
|
|
|
|
|
There are two ways to get a ZMR entry:
1. direct by ZMR
2. by ERnP marked as ZMR KITT entity
In case of we only get a result by option 2, the ZMR entry has to be updated with eIDAS documents again
|
|
and closed ERnP entries that kitt to ZMR entries
|
|
|
|
|
|
|
|
|
|
|
|
|
|
natural person in one single request
|
|
|