aboutsummaryrefslogtreecommitdiff
path: root/modules/authmodule-eIDAS-v2
AgeCommit message (Collapse)AuthorFilesLines
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
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 06:13:44 +0000