| Test Name | automatic-payments_api_sweeping-accounts-invalid-creditor_test-module_v2 |
|---|---|
| Variant | client_auth_type=private_key_jwt, fapi_auth_request_method=pushed, fapi_profile=openbanking_brazil, fapi_response_mode=plain_response |
| Test ID | 4hPE3x7vBvNG6Ba https://web.conformance.directory.openbankingbrasil.org.br/log-detail.html?public=true&log=4hPE3x7vBvNG6Ba |
| Created | 2025-04-22T13:09:11.420395357Z |
| Description | Banrisul - Conformidade Funcional |
| Test Version | 5.1.17 build: 110c5be81b38d74ed705b5339f0ebc2acce058a3 |
| Test Owner | katiele_souto@banrisul.com.br https://auth.sandbox.directory.openbankingbrasil.org.br |
| Plan ID | FLYTEaNLAcouD https://web.conformance.directory.openbankingbrasil.org.br/plan-detail.html?public=true&plan=FLYTEaNLAcouD |
| Exported From | https://web.conformance.directory.openbankingbrasil.org.br |
| Exported By | katiele_souto@banrisul.com.br https://auth.sandbox.directory.openbankingbrasil.org.br |
| Suite Version | 5.1.17 build: 110c5be81b38d74ed705b5339f0ebc2acce058a3 |
| Exported | 2025-04-22 18:07:15 (UTC) |
| Status: FINISHED Result: PASSED |
| SUCCESS 78 FAILURE 0 WARNING 0 REVIEW 0 INFO 1 |
| 2025-04-22 13:09:11 |
INFO
|
TEST-RUNNER
Test instance 4hPE3x7vBvNG6Ba created
|
||||||||||||||
|
||||||||||||||||
| 2025-04-22 13:09:11 |
SUCCESS
|
CreateRedirectUri
Created redirect URI
|
||
|
||||
| 2025-04-22 13:09:11 |
|
GetDynamicServerConfiguration
HTTP request
|
||||||||
|
||||||||||
| 2025-04-22 13:09:12 |
RESPONSE
|
GetDynamicServerConfiguration
HTTP response
|
||||||||
|
||||||||||
| 2025-04-22 13:09:12 |
SUCCESS
|
GetDynamicServerConfiguration
Successfully parsed server configuration
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2025-04-22 13:09:12 | SUCCESS |
AddMTLSEndpointAliasesToEnvironment
Added mtls_endpoint_aliases to environment
|
|
|
||
| 2025-04-22 13:09:12 |
SUCCESS
|
CheckServerConfiguration
Found required server configuration keys
|
||
|
||||
| 2025-04-22 13:09:12 |
|
FetchServerKeys
Fetching server key
|
||
|
||||
| 2025-04-22 13:09:12 |
|
FetchServerKeys
HTTP request
|
||||||||
|
||||||||||
| 2025-04-22 13:09:13 |
RESPONSE
|
FetchServerKeys
HTTP response
|
||||||||
|
||||||||||
| 2025-04-22 13:09:13 |
|
FetchServerKeys
Found JWK set string
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
FetchServerKeys
Found server JWK set
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
CheckServerKeysIsValid
Server JWKs is valid
|
||
|
||||
| 2025-04-22 13:09:13 | SUCCESS |
ValidateServerJWKs
Valid server JWKs: keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-04-22 13:09:13 | SUCCESS |
CheckForKeyIdInServerJWKs
All keys contain kids
|
|
|
||
| 2025-04-22 13:09:13 | SUCCESS |
EnsureServerJwksDoesNotContainPrivateOrSymmetricKeys
Jwks does not contain any private or symmetric keys
|
|
|
||
| 2025-04-22 13:09:13 | SUCCESS |
FAPIEnsureMinimumServerKeyLength
Validated minimum key lengths for server_jwks
|
||
|
||||
| Validating Well-Known URI |
| 2025-04-22 13:09:13 |
SUCCESS
|
CheckDiscEndpointDiscoveryUrl
discoveryUrl
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
EnsureWellKnownUriIsRegistered
Found Authorisation Server with provided Well-Known URL in the Directory Participants List
|
||||
|
||||||
| Validating Authorisation Server has supported Endpoint |
| 2025-04-22 13:09:13 |
SUCCESS
|
GetAuthServerFromParticipantsEndpoint
Found organisation
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
GetAuthServerFromParticipantsEndpoint
Found auth server from participants endpoint
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
GetAutomaticPaymentRecurringConsentV2Endpoint
Inserted consent endpoint into config
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
GetStaticClientConfiguration
Found a static client object
|
||||||||
|
||||||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
AddOpenIdScope
Added scope of 'customers accounts consents openid recurring-payments openid' to client's scope
|
||||||||
|
||||||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
ValidateMTLSCertificatesHeader
MTLS certificates header is valid
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
ExtractMTLSCertificatesFromConfiguration
Mutual TLS authentication credentials loaded
|
||||||
|
||||||||
| 2025-04-22 13:09:13 |
|
Scopes and Permissions Builder
ScopesAndPermissionsBuilder was correctly instantiated
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
Scopes and Permissions Builder:
Providing Permissions/Scopes:
|
||||
|
||||||
| 2025-04-22 13:09:13 | SUCCESS |
ValidateClientJWKsPrivatePart
Valid client JWKs: keys are valid JSON, contain the required fields, the private/public exponents match and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
ExtractJWKsFromStaticClientConfiguration
Extracted client JWK
|
||||
|
||||||
| 2025-04-22 13:09:13 | SUCCESS |
CheckForKeyIdInClientJWKs
All keys contain kids
|
|
|
||
| 2025-04-22 13:09:13 | SUCCESS |
CheckDistinctKeyIdValueInClientJWKs
Distinct 'kid' value in all keys of client_jwks
|
||
|
||||
| 2025-04-22 13:09:13 | SUCCESS |
FAPIBrazilCheckKeyAlgInClientJWKs
Keys in client JWKS all have permitted 'alg'
|
||
|
||||
| 2025-04-22 13:09:13 | SUCCESS |
FAPIEnsureMinimumClientKeyLength
Validated minimum key lengths for client_jwks
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
ValidateMTLSCertificatesAsX509
Mutual TLS authentication cert validated as X.509
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
AddRecurringPaymentResourceUrlToConfig
resourceUrl was added to the config
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
CreateSweepingRecurringConfigurationObjectWithOnlyAmount
The recurringConfiguration object has been created
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
AddRecurringPaymentConsentRequestBodyToConfig
Consent request body was added to the config
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
GetResourceEndpointConfiguration
Found a resource endpoint object
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
SetProtectedResourceUrlToSingleResourceEndpoint
Set protected resource URL
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
ExtractTLSTestValuesFromResourceConfiguration
Extracted TLS information from resource endpoint
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
ExtractTLSTestValuesFromOBResourceConfiguration
Extracted TLS information from resource endpoint
|
||||
|
||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
AddAutomaticPaymentToTheResource
Hardcoded brazilPixPayment object was added to the resource
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
SetAutomaticPaymentAmountTo300
The amount for the next automatic payment has been set
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
PrepareToPostConsentRequest
Call to consent API will be an HTTP POST
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
SetProtectedResourceUrlToRecurringPaymentsEndpoint
Endpoint added
|
||
|
||||
| 2025-04-22 13:09:13 |
SUCCESS
|
SaveConsentsBody
Consents request body has been saved
|
|
|
||
| 2025-04-22 13:09:13 |
|
automatic-payments_api_sweeping-accounts-invalid-creditor_test-module_v2
Setup Done
|
|
|
||
| POST consents sending the logged user not matching the creditor - Expects 422 DETALHE_PAGAMENTO_INVALIDO |
| 2025-04-22 13:09:13 |
SUCCESS
|
LoadConsentsBody
Consents request body has been loaded
|
|
|
||
| 2025-04-22 13:09:13 |
SUCCESS
|
EditRecurringPaymentsConsentBodyToSetInvalidCreditor
Updated first creditor to have a different identification
|
||||||
|
||||||||
| Use client_credentials grant to obtain Brazil consent |
| 2025-04-22 13:09:13 |
SUCCESS
|
CreateTokenEndpointRequestForClientCredentialsGrant
Created token endpoint request
|
||||
|
||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
SetRecurringPaymentsScopeOnTokenEndpointRequest
Set scope parameter to 'recurring-payments'
|
||||
|
||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
CreateClientAuthenticationAssertionClaims
Created client assertion claims
|
||||||||||||
|
||||||||||||||
| 2025-04-22 13:09:13 |
SUCCESS
|
SignClientAuthenticationAssertion
Signed the client assertion
|
||
|
||||
| 2025-04-22 13:09:13 |
|
AddClientAssertionToTokenEndpointRequest
Added client assertion
|
||||||||
|
||||||||||
| 2025-04-22 13:09:13 |
|
CallTokenEndpoint
HTTP request
|
||||||||||
|
||||||||||||
| 2025-04-22 13:09:14 |
RESPONSE
|
CallTokenEndpoint
HTTP response
|
||||||||
|
||||||||||
| 2025-04-22 13:09:14 |
SUCCESS
|
CallTokenEndpoint
Parsed token endpoint response
|
||||||||||
|
||||||||||||
| 2025-04-22 13:09:14 |
SUCCESS
|
CheckIfTokenEndpointResponseError
No error from token endpoint
|
|
|
||
| 2025-04-22 13:09:14 |
SUCCESS
|
CheckForAccessTokenValue
Found an access token
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
ExtractAccessTokenFromTokenResponse
Extracted the access token
|
||||
|
||||||
| 2025-04-22 13:09:14 | SUCCESS |
ExtractExpiresInFromTokenEndpointResponse
Extracted 'expires_in'
|
||
|
||||
| 2025-04-22 13:09:14 | SUCCESS |
ValidateExpiresIn
expires_in passed all validation checks
|
||
|
||||
| 2025-04-22 13:09:14 |
|
CreateEmptyResourceEndpointRequestHeaders
Created empty headers
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
AddFAPIAuthDateToResourceEndpointRequest
Added x-fapi-auth-date to resource endpoint request headers
|
||
|
||||
| 2025-04-22 13:09:14 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
CreateIdempotencyKey
Created idempotency key
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
AddIdempotencyKeyHeader
Added x-idempotency-key to resource endpoint request headers
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
CreatePaymentConsentRequest
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
FAPIBrazilExtractClientMTLSCertificateSubject
Extracted subject from MTLS certificate
|
||||||
|
||||||||
| 2025-04-22 13:09:14 | SUCCESS |
AddAudAsPaymentConsentUriToRequestObject
Added aud to request object claims
|
||
|
||||
| 2025-04-22 13:09:14 |
|
AddIssAsCertificateOuToRequestObject
Added iss value based on TLS certificate organizational unit to request object claims
|
||
|
||||
| 2025-04-22 13:09:14 | SUCCESS |
AddJtiAsUuidToRequestObject
Added jti to request object claims
|
||
|
||||
| 2025-04-22 13:09:14 | SUCCESS |
AddIatToRequestObject
Added iat to request object claims
|
||
|
||||
| 2025-04-22 13:09:14 |
SUCCESS
|
ValidateOrganizationJWKsPrivatePart
Valid organization JWKs: keys are valid JSON, contain the required fields, the private/public exponents match and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-04-22 13:09:14 |
SUCCESS
|
FAPIBrazilSignPaymentConsentRequest
Signed the request
|
||||||||
|
||||||||||
| 2025-04-22 13:09:14 |
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
HTTP request
|
||||||||||
|
||||||||||||
| 2025-04-22 13:09:16 |
RESPONSE
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
HTTP response
|
||||||||
|
||||||||||
| 2025-04-22 13:09:16 |
SUCCESS
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
Payment consent endpoint response
|
||||||||
|
||||||||||
| 2025-04-22 13:09:16 |
SUCCESS
|
EnsureConsentResponseCodeWas422
Correct status obtained
|
||
|
||||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up errors on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The errors element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up code on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The code element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up code on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The code element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up title on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The title element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up title on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The title element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up detail on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The detail element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up detail on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The detail element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up meta on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The meta element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up meta on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The meta element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up requestDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The requestDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
PostRecurringConsentOASValidatorV2
Looking up requestDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The requestDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido
Looking up errors on the EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido
The errors element is present in the EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido API response
|
|
|
||
| 2025-04-22 13:09:16 |
|
EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido
Looking up code on the EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido API response
|
|
|
||
| 2025-04-22 13:09:16 |
SUCCESS
|
EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido
The code element is present in the EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido API response
|
|
|
||
| 2025-04-22 13:09:17 |
SUCCESS
|
EnsureErrorResponseCodeFieldWasDetalhePagamentoInvalido
Found error with the expected code
|
||||
|
||||||
| 2025-04-22 13:09:17 |
FINISHED
|
automatic-payments_api_sweeping-accounts-invalid-creditor_test-module_v2
Test has run to completion
|
||
|
||||
| 2025-04-22 13:09:21 |
|
TEST-RUNNER
Alias has now been claimed by another test
|
||||
|
||||||