Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
address searching
|
|
|
|
'matching-by-address-search'
|
|
|
|
|
|
code and connector-specific elements
|
|
# Conflicts:
# basicConfig/templates/error_message.html
# modules/core_common_webapp/src/main/java/at/asitplus/eidas/specific/core/builder/AuthenticationDataBuilder.java
|
|
|
|
|
|
|
|
- The original version was not successful because BM.I services remove the ID from request
|
|
# Conflicts:
# build_reporting/pom.xml
# modules/authmodule-eIDAS-v2/pom.xml
|
|
data
|
|
|
|
communication
|
|
|
|
|
|
process engine
|