Last versions
Component |
tag |
artifact |
docker |
helm chart |
Change log |
Parent |
v2.0.0 |
2.0.0 |
|
|
2.0.0 |
Commons |
v2.0.3 |
2.0.3 |
|
|
2.0.3 |
IG |
v2.0.0 |
2.0.0 |
2.0.0 |
|
2.0.0 |
RCS |
v2.0.2 |
2.0.2 |
2.0.2 |
2.0.2 |
2.0.2 |
RS |
v2.0.2 |
2.0.2 |
2.0.2 |
2.0.2 |
2.0.2 |
RCS-UI |
v2.0.0 |
2.0.0 |
2.0.0 |
2.0.0 |
2.0.0 |
Functional Tests |
v2.0.2 |
|
2.0.2 |
|
|
Release 2.0.0
In the previous versions the business logic regarding consent flows are delegated to IG
as it is the component used to store the intents in IDM
but from the customer point of view could be tricky to understand which are the processes of filter routes,
from the current version the SAPIG will achieve the below specs
- The customer no need deep knowledge about IG
- Delegate to IG only these processes related with identity management, authorisation and authentication.
- Make Test Facility Bank (RS) more consistent for customers, they could want to build his own
Test Facility Bank (RS)
- Make easier for customers change the intent store component
- Make easier for customers customize the validations with their own validations
- Make easier extend the platform consent flow and access resources features
- Upgrade
IG
version to 7.2.0
- Upgrade routes to work with
Test Facility Bank (RS)
through a reverse proxy
- Clean up and removed OB Consent Biz logic filters and deprecated Filters
- Simplify routes and delegate to
IG
only these processes related with identity management, authorisation and authentication.
- Added new filter to validate the
intent_id
claim from access_token
against the consent id
from the request
- Added new routes to support
Confirmation of funds
API
Remote Consent Service (RCS) |
- Now is responsible to managing the consent objects in a MongoDB as dedicated consent store
- Expose a
Consent Store Client API
to be used by other components to do operations on consents
- Provides an Internal API to support the persistence operations for consents stored in mongoDB
Remote Consent Service User Interface (RCS-UI) |
- Support for
Confirmation of funds consent
PSU authorisation journey.
- Implements all consents and access resources OB APIs
- Extendable validation framework secure-api-gateway-ob-uk-rs-validation
- Added a register File payment service to manage file types payment processors, supported as default the OB file types defined, now the customer can register new custom file types to support different formats plugging custom file payment processors to process custom file types.
Confirmation of Funds API |
Release 2.0.1
- Upgrade helm charts of
Consent Resource Service (RCS)
and Test Facility Bank (RS)
to be aligned with pom version.
Release 2.0.2
Remote Consent Service (RCS) |
- Configuring
DateToUTCDateTimeConverter
to ensure that data retrieved from Mongo comes back as UTC
, otherwise equality checks fail as incoming data from the REST API is always UTC
- Adding
IDEMPOTENCY_ERROR
to the ConsentStoreClientException
so that it can be handled by the caller
- Check that duplicate requests using the same idempotency key have the same request body
- Fixed an
IllegalStateException
consent type is not supported when a PSU submit a consent decision.
- Defaulting
rs.data.upload.limit.events
property in the annotation to 10. This makes upgrading easier for extensions projects which have their own spring configuration file.
- The
FileParseException
does not allow implementations enough flexibility in choosing specific error codes to return to the user. Changing processFileImpl
method to throw OBErrorException
so that subclasses are able to specify the errorCode.
- Fix discovery endpoint implementation to display event notification APIs.