aboutsummaryrefslogtreecommitdiff
path: root/modules/authmodule-eIDAS-v2
AgeCommit message (Collapse)AuthorFilesLines
2023-06-07chore(ernp): switch to ERnP REST API version 2.0.3Thomas2-11/+4
Remove configuration property to disable new API elements
2023-06-07fix(ernp): change JSON API because it has some bugsThomas20-95/+95
Reason: some elements are 'date' now, but was defined as 'date-time'
2023-06-07feat(ernp): switch to new ERnP REST API v2.0.3(2023) that implements ↵Thomas5-52/+549
"Meldegesetznovelle 2023)
2023-06-07feat(srz): switch to new SZR WSDL v4.1(2023) that implements ↵Thomas15-3148/+663
"Meldegesetznovelle 2023)
2023-06-05build(core): switch to next snapshot versionThomas1-1/+1
2023-06-05build(core): switch to next release versionproxyservice_1.0.4Thomas1-1/+1
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-22chore(core): update third-party libsThomas1-7/+7
Inlcude Spring 5.3.26 to fix CVE-2023-20859, CVE-2023-20861, CVE-2023-20860
2023-03-02build(core): switch to next snapshot versionThomas1-1/+1
2023-03-02fix(connector): mitigate possible NullPointerExceptionproxyservice_1.0.3connector_1.3.8Thomas1-1/+2
2023-03-02build(core): switch to next release versionThomas1-1/+1
2023-03-02feat(connector): make nameIdFormat configurable for earch citizen countryThomas4-5/+67
2023-02-28fix(matching): remove HTML escapetion from address-searchThomas2-2/+31
Reason: special characters are requiered in plain text
2023-02-28test(ernp): check some more elements on ERnP Update requestThomas2-1/+5
2023-02-27fix(ernp): set full person info in case of MDS updateThomas4-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-26test(ernp): add test-case that requests MDS for Austrian test-identityThomas2-0/+42
2023-01-16build(core): switch to next snapshot versionThomas1-1/+1
2023-01-16build(core): switch to next release version for MS-Connectorconnector_1.3.7Thomas1-1/+1
2022-12-22build(core): switch to next snapshot versionThomas1-1/+1
2022-12-19build(core): switch to next release versionproxyservice_1.0.2connector_1.3.6Thomas1-1/+1
2022-12-19feat(eidas-connector): support not-notified LoAThomas8-58/+261
- not-notified LoA is currently used by Ukraine
2022-12-15feat(connector): add support for Ukraine eIDAS-ProxyServiceThomas4-0/+118
Since Ukraine is not notified, we need a new configuration parameter to set not-notified LoA
2022-12-01test(matching): check UX screen for 'disallowed new ERnP entry by user'Thomas1-0/+28
2022-12-01build(core): switch to next snapshot versionThomas1-1/+1
2022-12-01build(core): switch to next release versionproxyservice_1.0.1Thomas1-1/+1
2022-12-01style(matching): fix code-style issue in ERnP clientThomas1-12/+13
2022-12-01test(matching): fix broken jUnit test after refactoring of OperationStatusThomas1-11/+11
2022-12-01feat(matching): disable UX option to create a new ERnP entry if it was ↵Thomas5-13/+98
prohibited by matching-process
2022-12-01feat(matching): add flag 'allowNewErnpEntryByUser' into intermediate ↵Thomas6-36/+169
matching-result That flag disable a new ERnP entry by user decision
2022-12-01feat(ernp): change handling of entities with status "PersonAmtlichBeenden" againThomas2-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-01fix(matching): change processing order in case of single entity selection ↵Thomas4-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-30feat(ida): remove NameIdPolicy PERSISTENT from IDA SAML2 requestThomas1-6/+5
Reason: The IDA Shibboleth IDP does not support PERSISTENT yet
2022-11-21build(core): switch to next snapshot versionThomas1-1/+1
2022-11-21build(core): switch to next release versionconnector_1.3.5Thomas1-1/+1
2022-11-17style(core): fix some code-style issuesThomas2-4/+5
2022-11-17feat(connector): add validation to disable private-SP support for specific ↵Thomas14-33/+165
countries
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