Adapt @tobypinder / Credit Kudos client application as a standalone instance, to go through the following procedures for each bank brand
A1 - initiate a client credentials grant (calls authorisation server)
A2 - POST to /payment-order-consents (calls resource server)
A3 - GET /payment-order-consents (calls resource server)
(the specific payment resource can be varied)
B1 - initiate a client credentials grant (calls authorisation server)
B2 - POST to /account-access-consents (calls resource server)
B3 - GET /account-access-consents/ (calls resource server)
B4 - DELETE /account-access-consents
C1 - call PSU authentication portal
All of these calls can take place in the absence of a customer authenticated journey. The response times from each resource will need to be recorded.
These calls should also feed information to the availability monitoring solution
Adapt @tobypinder / Credit Kudos client application as a standalone instance, to go through the following procedures for each bank brand
A1 - initiate a client credentials grant (calls authorisation server) A2 - POST to /payment-order-consents (calls resource server) A3 - GET /payment-order-consents (calls resource server)
(the specific payment resource can be varied)
B1 - initiate a client credentials grant (calls authorisation server) B2 - POST to /account-access-consents (calls resource server) B3 - GET /account-access-consents/ (calls resource server) B4 - DELETE /account-access-consents
C1 - call PSU authentication portal
All of these calls can take place in the absence of a customer authenticated journey. The response times from each resource will need to be recorded.
These calls should also feed information to the availability monitoring solution