Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
Reason: The IDA Shibboleth IDP does not support PERSISTENT yet
|
|
|
|
|
|
|
|
countries
|
|
|
|
|
|
and automated
|
|
|
|
by user decision
|
|
|
|
|
|
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
|
|
|
|
|
|
In case of KITT between ERnP and ZMR entries it's possible to get the same entity
in both results. Remove ERnP result if ZMR results contains a person with
same bPK.
|
|
to be started manually
|
|
|
|
ZMR and ERnP always return the latest version of an entity.
However, that latest version can also have status closed and in that case
the entity is not valid any more.
|
|
|
|
|
|
The ID Austria system changes the format of technical AuthBlock
with Frontend/Backend interface-specification v1.1.0
|
|
about matching process
|
|
# Conflicts:
# ms_specific_proxyservice/src/test/resources/config/logback_config.xml
|
|
|
|
|
|
|
|
create-new-ERnP-entry operation
|