Open Banking registration error

Hi, I’m trying to setup a new software statement using dynamic registration and I’m getting an odd error:

{"error":"invalid_request","error_description":"Failed to parse and validate request JWT: bad_request.token_endpoint_auth_signing_alg: Must be empty","error_params":{"original_error_code":"bad_request.JWT"}}

It’s not clear from your documentation what I should set as the algorithm, providing an empty string of nil value also raises an error :man_shrugging:

Hey @mattrayner, are you an approved Open Banking AISP?

If so, just to quote @kieranmch from a previous thread:

I am yes, the docs said to post here :joy:

2 Likes

Interesting :face_with_monocle: I’d disregard that for now and use the open banking inbox instead.

I’ll feed it back to the team that the docs may need updating :sweat_smile:

For any OB queries please use our inbox :slight_smile: Where in the docs does it say this? I can get it corrected.

Hi Kieran, its in the first paragraph off the docs, I can see that later in the open banking references there is also a link to email you too, but I read from the top down so saw the forum link first :smiley:

Open banking is so “open” that everyone tries to explicitly bury any information about it into non-public channels. :thinking:

I don’t think that’s a fair statement. We centralise support for Open Banking companies in one place to ensure that people get fast replies directly from specialists, we have appropriate support records, we can track what people are contacting us over, and we can have discussions that may be commercially sensitive to the companies approaching us. The forum isn’t the place to do that.

10 Likes