Introduction
At IESG on 21 March 2019, a question was raised about 'resilience challenges with PIS' use cases and 'how this could be measured'. The Implementation Trustee set an action for TDA to address the issue of resilience and report back to IESG. In parallel, TDA had already been looking at a number of other issues which were causing loss of access for TPPs.
There were also a number of other related issues being raised at the same time in various forums (including the TDA, API Forum, Testing Working Group and the EBA Working Group) relating to overall ecosystem resilience, including dependencies on the directory, lack of consistent approach to implementation, drop off rates during authentication and overall lack of functionality. Therefore, when TDA members were asked to comment on resilience, a number of these other issues were raised as being equally, if not more, important for certain use cases. TDA members have thus contributed to create a long list of these issues.
This paper is a collation of these issues, and for each, details on the route causes, impact (on the end PSU), mitigating actions and the current status. The paper also includes a number of recommendations.
Ecosystem resilience
While the overall ecosystem has a dependency on the OBIE Directory, the impact is low if this is not available for periods of time, as ASPSPs must not block access to authorised TPPs based solely on Directory outages and should cache (locally in their systems) any critical directory services, especially if they chose to rely on the data from these to be highly available and/or validated for every API call.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Agreed actions
The UK ecosystem is still young, especially regarding the introduction and take-up of PISP services. Therefore , therefore these issues should be subject to continual updates and regular review. The following actions were agreed by the Implementation Trustee at IESG on 25 July 2019:
- These issues should are to be made public on the OBIE Developer Zone. All of these issues are well known, widely reported, and complete transparency is the best way to encourage positive remedial actions.
- Actions and status should will be tracked as a standing agenda item at TDA, and only escalated to IESG where relevant.
- All participants should continue to report specific issues (e.g. relating to a specific TPP-ASPSP integration) to OBIE via a service desk ticket.
...