aboutsummaryrefslogtreecommitdiff
path: root/modules/authmodule-eIDAS-v2/src/main/java
AgeCommit message (Collapse)AuthorFilesLines
2023-06-07feat(ernp): switch to new ERnP REST API v2.0.3(2023) that implements ↵Thomas2-5/+38
"Meldegesetznovelle 2023)
2023-06-07feat(srz): switch to new SZR WSDL v4.1(2023) that implements ↵Thomas2-55/+57
"Meldegesetznovelle 2023)
2023-06-05chore(matching): optimize error handling for matching by ID AustriaThomas1-1/+4
2023-06-05feat(matching): log BM.I specific response headers 'txId' and 'pvp-txId'Thomas3-20/+70
2023-03-02fix(connector): mitigate possible NullPointerExceptionproxyservice_1.0.3connector_1.3.8Thomas1-1/+2
2023-03-02feat(connector): make nameIdFormat configurable for earch citizen countryThomas2-4/+16
2023-02-28fix(matching): remove HTML escapetion from address-searchThomas1-2/+4
Reason: special characters are requiered in plain text
2023-02-27fix(ernp): set full person info in case of MDS updateThomas1-25/+60
ERnP does not support partial personData updates. Therefore, we have to copy the latest ERnP result to all information during an update request.
2022-12-19feat(eidas-connector): support not-notified LoAThomas5-45/+113
- not-notified LoA is currently used by Ukraine
2022-12-15feat(connector): add support for Ukraine eIDAS-ProxyServiceThomas1-0/+68
Since Ukraine is not notified, we need a new configuration parameter to set not-notified LoA
2022-12-01style(matching): fix code-style issue in ERnP clientThomas1-12/+13
2022-12-01feat(matching): disable UX option to create a new ERnP entry if it was ↵Thomas3-4/+21
prohibited by matching-process
2022-12-01feat(matching): add flag 'allowNewErnpEntryByUser' into intermediate ↵Thomas1-12/+43
matching-result That flag disable a new ERnP entry by user decision
2022-12-01feat(ernp): change handling of entities with status "PersonAmtlichBeenden" againThomas1-17/+37
- filter all entries that are marked as "PersonAmtlichBeenden" - set flag 'allowNewErnpEntryByUser' to false in case of matching steps that requires single hit
2022-12-01fix(matching): change processing order in case of single entity selection ↵Thomas1-17/+17
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
2022-11-30feat(ida): remove NameIdPolicy PERSISTENT from IDA SAML2 requestThomas1-6/+5
Reason: The IDA Shibboleth IDP does not support PERSISTENT yet
2022-11-17style(core): fix some code-style issuesThomas2-4/+5
2022-11-17feat(connector): add validation to disable private-SP support for specific ↵Thomas8-24/+95
countries
2022-11-17test(core): optimize jUnit tests to get better test coverageThomas4-6/+19
2022-10-21test(matching): add some more validations for advanced statistic logThomas1-2/+2
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 ↵Thomas3-3/+23
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 onlyThomas2-3/+9
2022-10-17feat(mathing): join ZMR results and ERnP-to-ZMR-KITT resultsThomas1-10/+33
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 ↵Thomas2-34/+145
and closed ERnP entries that kitt to ZMR entries
2022-10-11feat(matching): clearing in case of ZMR and ERnP result contains the same personThomas1-2/+23
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-07fix(eIDAS-ERnP): eIDAS documents can by 'null' in ERnP responseThomas1-2/+6
2022-10-07feat(matching): check ZMR and ERnP response if enities are closedThomas3-27/+135
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-25feat(eidas): add support for new IDA AuthBlock formatThomas1-80/+130
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_serviceThomas3-67/+11
# Conflicts: # ms_specific_proxyservice/src/test/resources/config/logback_config.xml
2022-08-01fix(eidas): unset flag on execution-context that probibits ↵Thomas1-0/+1
create-new-ERnP-entry operation
2022-07-12refact(szr): only use alreadymatched eID data for SZR communicationThomas2-67/+10
2022-07-05Merge branch 'nightlybuild' into feature/ms_proxy_serviceThomas11-38/+166
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 resultsThomas9-10/+50
2022-07-01fix(matching): add null-check in custom comperator for address-search resultsThomas1-3/+9
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 resultsThomas1-28/+50
2022-07-01feat(matching): add configuration property to disable ↵Thomas4-4/+32
'matching-by-address-search'
2022-06-03refactor(eidas): split 'authmodule-eIDAS-v2' into 'common-eidas'Thomas16-330/+244
code and connector-specific elements
2022-06-03Merge branch 'feature/eidasnode_v2.6' into feature/ms_proxy_before_refactoringThomas1-7/+18
# Conflicts: # basicConfig/templates/error_message.html # modules/core_common_webapp/src/main/java/at/asitplus/eidas/specific/core/builder/AuthenticationDataBuilder.java
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_refactoringThomas4-20/+142
# Conflicts: # build_reporting/pom.xml # modules/authmodule-eIDAS-v2/pom.xml
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 ↵Thomas2-2/+92
communication
2022-05-16fix(matching): optimize prozess handling during alternative eIDAS authenticationThomas1-10/+27
2022-05-13fix(matching): set flag into process context to prohibit warning from ↵Thomas1-0/+1
process engine