Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-01-29 | refact(core): rename status-code class for revision logging | Thomas | 3 | -17/+17 | |
2024-01-26 | feat(eidas): refactoring to eIDAS node v2.7 | Thomas | 7 | -22/+23 | |
2023-10-11 | test(zmr): fix some tests after update to latest ZMR Web-Service API | Thomas | 4 | -4/+0 | |
2023-10-10 | feat(zmr):switch to new ZMR SOAP API from 2023.02.13 that implements ↵ | Thomas | 19 | -82/+480 | |
"Meldegesetznovelle 2023 | |||||
2023-10-09 | feat(srz): switch to new SZR WSDL v4.1.1 from 2023.10.09 | Thomas | 5 | -70/+70 | |
2023-10-09 | feat(ernp): switch to lastest ERnP openAPI version 2.6.0 | Thomas | 1 | -0/+7 | |
2023-09-25 | feat(ernp): switch to lastest ERnP openAPI version 2.5.2 | Thomas | 1 | -90/+302 | |
2023-06-07 | chore(ernp): switch to ERnP REST API version 2.0.3 | Thomas | 2 | -11/+4 | |
Remove configuration property to disable new API elements | |||||
2023-06-07 | fix(ernp): change JSON API because it has some bugs | Thomas | 20 | -95/+95 | |
Reason: some elements are 'date' now, but was defined as 'date-time' | |||||
2023-06-07 | feat(ernp): switch to new ERnP REST API v2.0.3(2023) that implements ↵ | Thomas | 5 | -52/+549 | |
"Meldegesetznovelle 2023) | |||||
2023-06-07 | feat(srz): switch to new SZR WSDL v4.1(2023) that implements ↵ | Thomas | 14 | -3147/+662 | |
"Meldegesetznovelle 2023) | |||||
2023-06-05 | chore(matching): optimize error handling for matching by ID Austria | Thomas | 1 | -1/+4 | |
2023-06-05 | feat(matching): log BM.I specific response headers 'txId' and 'pvp-txId' | Thomas | 3 | -20/+70 | |
2023-03-22 | chore(core): update third-party libs | Thomas | 1 | -7/+7 | |
Inlcude Spring 5.3.26 to fix CVE-2023-20859, CVE-2023-20861, CVE-2023-20860 | |||||
2023-03-02 | fix(connector): mitigate possible NullPointerExceptionproxyservice_1.0.3connector_1.3.8 | Thomas | 1 | -1/+2 | |
2023-03-02 | feat(connector): make nameIdFormat configurable for earch citizen country | Thomas | 4 | -5/+67 | |
2023-02-28 | fix(matching): remove HTML escapetion from address-search | Thomas | 2 | -2/+31 | |
Reason: special characters are requiered in plain text | |||||
2023-02-28 | test(ernp): check some more elements on ERnP Update request | Thomas | 2 | -1/+5 | |
2023-02-27 | fix(ernp): set full person info in case of MDS update | Thomas | 4 | -25/+270 | |
ERnP does not support partial personData updates. Therefore, we have to copy the latest ERnP result to all information during an update request. | |||||
2023-01-26 | test(ernp): add test-case that requests MDS for Austrian test-identity | Thomas | 2 | -0/+42 | |
2022-12-19 | feat(eidas-connector): support not-notified LoA | Thomas | 8 | -58/+261 | |
- not-notified LoA is currently used by Ukraine | |||||
2022-12-15 | feat(connector): add support for Ukraine eIDAS-ProxyService | Thomas | 4 | -0/+118 | |
Since Ukraine is not notified, we need a new configuration parameter to set not-notified LoA | |||||
2022-12-01 | test(matching): check UX screen for 'disallowed new ERnP entry by user' | Thomas | 1 | -0/+28 | |
2022-12-01 | style(matching): fix code-style issue in ERnP client | Thomas | 1 | -12/+13 | |
2022-12-01 | test(matching): fix broken jUnit test after refactoring of OperationStatus | Thomas | 1 | -11/+11 | |
2022-12-01 | feat(matching): disable UX option to create a new ERnP entry if it was ↵ | Thomas | 5 | -13/+98 | |
prohibited by matching-process | |||||
2022-12-01 | feat(matching): add flag 'allowNewErnpEntryByUser' into intermediate ↵ | Thomas | 6 | -36/+169 | |
matching-result That flag disable a new ERnP entry by user decision | |||||
2022-12-01 | feat(ernp): change handling of entities with status "PersonAmtlichBeenden" again | Thomas | 2 | -22/+46 | |
- filter all entries that are marked as "PersonAmtlichBeenden" - set flag 'allowNewErnpEntryByUser' to false in case of matching steps that requires single hit | |||||
2022-12-01 | fix(matching): change processing order in case of single entity selection ↵ | Thomas | 4 | -17/+235 | |
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-30 | feat(ida): remove NameIdPolicy PERSISTENT from IDA SAML2 request | Thomas | 1 | -6/+5 | |
Reason: The IDA Shibboleth IDP does not support PERSISTENT yet | |||||
2022-11-17 | style(core): fix some code-style issues | Thomas | 2 | -4/+5 | |
2022-11-17 | feat(connector): add validation to disable private-SP support for specific ↵ | Thomas | 14 | -33/+165 | |
countries | |||||
2022-11-17 | test(core): optimize jUnit tests to get better test coverage | Thomas | 8 | -10/+62 | |
2022-10-21 | test(matching): add some more validations for advanced statistic log | Thomas | 4 | -5/+33 | |
2022-10-21 | test(matching): fix broken test after distiguish between insert ERnP by user ↵ | Thomas | 1 | -2/+5 | |
and automated | |||||
2022-10-21 | feat(matching): add detailed matching results into JSON based statistic logger | Thomas | 7 | -3/+135 | |
2022-10-21 | feat(matching): distiguish between create ERnP entry by automated process or ↵ | Thomas | 5 | -6/+85 | |
by user decision | |||||
2022-10-17 | style(matching): fix some code-style issues | Thomas | 3 | -259/+274 | |
2022-10-17 | feat(zmr): requesting latest version for ZMR update by using bPK only | Thomas | 3 | -3/+117 | |
2022-10-17 | feat(mathing): join ZMR results and ERnP-to-ZMR-KITT results | Thomas | 2 | -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-17 | freat(ernp): update ERnP client to distiguish between active ERnP entries ↵ | Thomas | 6 | -40/+232 | |
and closed ERnP entries that kitt to ZMR entries | |||||
2022-10-11 | feat(matching): clearing in case of ZMR and ERnP result contains the same person | Thomas | 2 | -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-10 | test(zmr): remove some specific test-cases from integration tests that have ↵ | Thomas | 1 | -53/+0 | |
to be started manually | |||||
2022-10-07 | fix(eIDAS-ERnP): eIDAS documents can by 'null' in ERnP response | Thomas | 3 | -2/+100 | |
2022-10-07 | feat(matching): check ZMR and ERnP response if enities are closed | Thomas | 13 | -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-25 | feat(eidas): add support for new IDA AuthBlock format | Thomas | 3 | -89/+598 | |
The ID Austria system changes the format of technical AuthBlock with Frontend/Backend interface-specification v1.1.0 | |||||
2022-08-22 | chore(matching): add log-messages on level INFO to get more information ↵ | Thomas | 6 | -7/+31 | |
about matching process | |||||
2022-08-02 | Merge branch 'nightlybuild' into feature/ms_proxy_service | Thomas | 6 | -82/+44 | |
# Conflicts: # ms_specific_proxyservice/src/test/resources/config/logback_config.xml | |||||
2022-08-02 | test(matching): optimize validation of execution-context parameters | Thomas | 1 | -5/+22 | |
2022-08-01 | fix(eidas): unset flag on execution-context that probibits ↵ | Thomas | 2 | -2/+5 | |
create-new-ERnP-entry operation |