aboutsummaryrefslogtreecommitdiff
path: root/modules/authmodule-eIDAS-v2
AgeCommit message (Collapse)AuthorFilesLines
2022-11-17test(core): optimize jUnit tests to get better test coverageThomas8-10/+62
2022-10-21test(matching): add some more validations for advanced statistic logThomas4-5/+33
2022-10-21test(matching): fix broken test after distiguish between insert ERnP by user ↵Thomas1-2/+5
and automated
2022-10-21feat(matching): add detailed matching results into JSON based statistic loggerThomas7-3/+135
2022-10-21feat(matching): distiguish between create ERnP entry by automated process or ↵Thomas5-6/+85
by user decision
2022-10-17style(matching): fix some code-style issuesThomas3-259/+274
2022-10-17feat(zmr): requesting latest version for ZMR update by using bPK onlyThomas3-3/+117
2022-10-17feat(mathing): join ZMR results and ERnP-to-ZMR-KITT resultsThomas2-13/+150
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
2022-10-17freat(ernp): update ERnP client to distiguish between active ERnP entries ↵Thomas6-40/+232
and closed ERnP entries that kitt to ZMR entries
2022-10-13build(core): switch to next snapshot versionThomas1-1/+1
2022-10-13build(core): switch to next release version of MS-Connectorconnector_1.3.4Thomas1-1/+1
2022-10-11feat(matching): clearing in case of ZMR and ERnP result contains the same personThomas2-5/+48
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.
2022-10-10test(zmr): remove some specific test-cases from integration tests that have ↵Thomas1-53/+0
to be started manually
2022-10-07fix(eIDAS-ERnP): eIDAS documents can by 'null' in ERnP responseThomas3-2/+100
2022-10-07feat(matching): check ZMR and ERnP response if enities are closedThomas13-27/+1921
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.
2022-08-25build(core): switch to next snapshot versionThomas1-1/+1
2022-08-25build(core): switch to next release versionproxyservice_1.0.0connector_1.3.3Thomas1-1/+1
2022-08-25feat(eidas): add support for new IDA AuthBlock formatThomas3-89/+598
The ID Austria system changes the format of technical AuthBlock with Frontend/Backend interface-specification v1.1.0
2022-08-22chore(matching): add log-messages on level INFO to get more information ↵Thomas6-7/+31
about matching process
2022-08-02Merge branch 'nightlybuild' into feature/ms_proxy_serviceThomas7-83/+45
# Conflicts: # ms_specific_proxyservice/src/test/resources/config/logback_config.xml
2022-08-02build: switch to next snapshot versionThomas1-1/+1
2022-08-02build: switch to next release version1.3.2Thomas1-1/+1
2022-08-02test(matching): optimize validation of execution-context parametersThomas1-5/+22
2022-08-01fix(eidas): unset flag on execution-context that probibits ↵Thomas2-2/+5
create-new-ERnP-entry operation
2022-07-12refact(szr): only use alreadymatched eID data for SZR communicationThomas4-78/+20
2022-07-05Merge branch 'nightlybuild' into feature/ms_proxy_serviceThomas17-48/+289
2022-07-05build(core): switch to next snapshot versionThomas1-1/+1
2022-07-05build(core): switch to next release version1.3.1Thomas1-1/+1
2022-07-01style(matching): fix code-style issueThomas7-16/+16
2022-07-01refact(matching): make address-search sort result more resistentThomas1-7/+12
2022-07-01feat(core): update statistic-logger to include matching resultsThomas10-10/+61
2022-07-01fix(matching): add null-check in custom comperator for address-search resultsThomas2-4/+11
2022-07-01feat(matching): add configuration property to define max. results for ↵Thomas2-2/+28
address searching
2022-07-01feat(matching): optimize order of address search resultsThomas2-28/+105
2022-07-01feat(matching): add configuration property to disable ↵Thomas8-13/+87
'matching-by-address-search'
2022-06-03chore(config): split default configuration into MS-Connector and MS-Proxy-ServieThomas1-3/+3
2022-06-03test(core): add smoke test with full eIDAS OutGoing login and error-handlingThomas1-39/+0
2022-06-03refactor(eidas): split 'authmodule-eIDAS-v2' into 'common-eidas'Thomas35-499/+354
code and connector-specific elements
2022-06-03Merge branch 'feature/eidasnode_v2.6' into feature/ms_proxy_before_refactoringThomas18-8/+1372
# Conflicts: # basicConfig/templates/error_message.html # modules/core_common_webapp/src/main/java/at/asitplus/eidas/specific/core/builder/AuthenticationDataBuilder.java
2022-05-24chore(eidas): switch to version 2.6.0 of eIDAS Reference ImplementationThomas16-0/+1353
2022-05-24build: switch to next snapshot versionThomas1-1/+1
2022-05-19build: switch to next release version1.3.0Thomas1-1/+1
2022-05-18chore(register): update BM.I specific SOAP extension for transactionIdsThomas1-7/+18
- The original version was not successful because BM.I services remove the ID from request
2022-05-17Merge branch 'nightlybuild' into feature/ms_proxy_before_refactoringThomas9-307/+334
# Conflicts: # build_reporting/pom.xml # modules/authmodule-eIDAS-v2/pom.xml
2022-05-17test(eidas): fix broken test that checks post-processing for greece specific ↵Thomas1-1/+1
data
2022-05-17refact(ernp): use unique transactionId without suffix for ERnP communicationThomas1-8/+23
2022-05-17feat(register): inject unique transactionId as SOAP header for ZMR and SZR ↵Thomas3-2/+95
communication
2022-05-16fix(matching): optimize prozess handling during alternative eIDAS authenticationThomas5-293/+216
2022-05-13build(qs): update code-coverage checks againThomas1-0/+4
2022-05-13fix(matching): set flag into process context to prohibit warning from ↵Thomas1-0/+1
process engine