Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

This page lists previous certifications relating to the now deprecated Open Banking Security Profile.

Please see Security Profile Conformance for current certifications.

Previous guidance


Expand

An OBIE Security Profile Conformance Certificate allows an Implementer to demonstrate that they have successfully implemented the Open Banking Security Profile using the Open Banking Security Profile Conformance Tool (available till 14 Sep 2019).

Please visit the Open ID Foundation for certificates relating to the Financial Grade API (FAPI) Profile and Client Initiated Backchannel Authentication (CIBA) ProfileThe FAPI Profile is intended to replace the Open Banking Security Profile, and therefore an Implementer will not normally need to apply for certification for both profiles at the same time.

Pre-requisites

For Open Banking Security Profile Conformance Certificates:

  • Although the Implementer may download and run tests locally, Conformance Certificates will only be issued when the tests have been run and evidence supplied using the hosted version of the Open Banking Security Profile Conformance Tool .
  • The Implementer must have implemented the Open Banking Security Profile and use the Conformance Tool to test their implementation.
  • The Implementer must use the latest or most recent previously published version of the Conformance Tool
  • The Implementer must ensure that all sensitive information (e.g. private keys and authorisation headers) are redacted or removed prior to submission to OBIE.
  • OBIE will not normally publish new versions of the tool more frequently than every two weeks.
  • The tool will which generate a file which includes:
    • List of all tests run.
    • For each test run, a description, pass/fail flag, and link to the relevant specification reference.
  • The Implementer must also complete a signed attestation form to confirm that all evidence submitted is accurate and has not been altered in any way.

Number of Conformance Certificates needed

It is up to each Implementer as to how many Conformance Certificates they apply for.

For ASPSPs, each Conformance Certificate covers one base URL (e.g. api.bank.com). This URL may include multiple brands and/or products, based on the same Security Profile. It is up to the Implementer to ensure they have run and submitted sufficient tests which cover all relevant brands/products as part of their Conformance Certification Request.

An ASPSP may have other brands/products on separate base URLs which have the exact same functionality, and may decide to declare that these bands/products are also covered by a single Conformance Certificate. However OBIE will only publish the Conformance Certificate based on the single base URL submitted by the Implementer.

Open Banking Security Profile Certifications (version 3 of the OBIE Standard)

...

Expand


ASPSP/BrandSecurity Profile VersionSuite VersionClient Authentication TypeResponse TypeDate

Submission

Status#Warning#FailedNotes

AIB Group (UK) p.l.c. / First Trust Bank

v1.1.1v1.1.7Client secret basiccode id_token
 
Download
Status
colourGreen
titlePass
10
Bank of Ireland









Barclaysv1.1.1v1.1.10client secret basic, client secret postcode Download
Status
colourYellow
titleProvisional
22
scope not present in token response  ->  Agreed with OBIE that it is not a breaking defect
·         This is a limitation of the current software version for the platform, and will be resolved in the next release..
Error from account request endpoint (406 Error) -> Expected Error because of incorrect values in Headers (Swagger v/s FAPI standards)
·         We currently check for application/json being present within the headers only as a strict interpretation as per Swagger / OBIE specifications and not to the FAPI standard
Danske









HSBCv1.1.2v1.1.11Client secret basiccode, code id_token Download
Status
colourGreen
titlePass
20
First Direct Bankv1.1.2v1.1.11Client secret basiccode, code id_token Download
Status
colourGreen
titlePass
2

Marks and Spencer Bankv1.1.2v1.1.11Client secret basiccode, code id_token Download
Status
colourGreen
titlePass
2

Lloyds Bankv1.1.1v1.1.9Client secret basic, client secret postcode, code id_token Download
Status
colourGreen
titlePass
11NB: Platform currently unable to handle query parameters in redirect URI. To be resolved. 1 test still to be run. Non-blocking issue. 
Nationwidev1.1.2v1.1.9Client secret basiccode id_token Download
Status
colourGreen
titlePass
11NB: Platform currently unable to handle query parameters in redirect URI. Incorrect error returned in response to access token sent as a query parameter. Both issues shortly to be resolved. Platform accepts TLS1.0&1.1 connections due to limitations in customer base. 
RBS









Santanderv1.1.1v1.1.11client secret basiccode id_token Download
Status
colourGreen
titlePass
10
Ozone (Mock Bank)v1.1.2v1.1.7client secret basic, client secret post, private keycode, code id_token Download
Status
colourGreen
titlePass
10See O3-Ozone
Forgerock (Platform Vendor and Sandbox Provider)v1.1.2v1.1.9Private keycode, code id_token Download
Status
colourGreen
titlePass
10See https://backstage.forgerock.com/knowledge/openbanking/home
Ostia Solutions (Sandbox Provider)v1.1.2v1.1.9Private keycode Download
Status
colourGreen
titlePass
00See Ostia Solutions


Key
ASPSPOP tests
TPPRP tests
Vendor/TSP OP and/or RP tests
Status
colourGreen
titlePass
Pass with no failures
Status
colourYellow
titleProvisional
One or more failures where there is an agreed (by standards body or regulator) workaround/mitigation
Status
colourRed
titleFail
One or more failures where there is no agreed workaround/mitigation


...