Versions Compared

Old Version 4

changes.mady.by.user Timothy Perkins

Saved on

compared with

New Version 5

changes.mady.by.user Timothy Perkins

Saved on

Key

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

...

Change to Production:

Improvement

Delivery date

Client Registration support for private_key_jwt:

TPPs will need to register specifying private_key_jwt as the token_endpoint_auth_method (as shown through our Open ID Configuration.) Note: Clients already registered with client_secret_post and client_secret_basic will be able to continue requesting tokens with their respective method. The intention is that the TPPs currently using client_secret_basic and client_secret_post will be asked to update clients to use private_key_jwt in the future.

 



On-boarding

Supports dynamic client registration (Y/N)Y
Instructions for manual onboardingN/A
OIDC .well-known endpoint

https://integrations.capitalone.co.uk/.well-known/openid-configuration

Notes on testingTPPs must be registered with the Open Banking Directory
Other on-boarding notes
  • There is currently no support for Client Management
  • SSA must be issued by Open Banking
  • redirect_uris MUST match or be a subset of the software_redirect_uris claim in the SSA
  • See well-known endpoint for supported configurations
  • When onboarding if any challenges arise please contact ukdevelopersupport@capitalone.com

  • private_key_jwt must be specified as the the token_endpoint_auth_method
Documentation URL


https://developer.capitalone.co.uk/api/

...