request-target | A url parser for http requests , compliant with RFC | Parser library

We use Chilkat to sign HTTP requests in our Powerbuilder 9.0.3 application (and also powerbuilder 12.6) but it's like the signature generated by Chilkat is not accepted by the API of Isabel (we already have contacted Isabel and they guess that there is a parameters issue in the signature algorithm). The documentation of the Isabel API (https://documentation.ibanity.com/http-signature)say that we have to use the RSASSA-PSS signature algorithm with the following parameters.

• Hash algorithm: SHA-256
• Mask generation function: MGF1 Mask
• generation algorithm: SHA-256
• Salt length: 32 bytes (= 256 bits, same as the hash length)
• Trailer field: 1

and so we have set the chilkat Rsa component like this:

I have a Go app that use Gin gonic and a Nginx reverse proxy that send trafic to another app on domain.com and send all the *.domain.com subdomains traffic directly to my go app.

My Go app then has a middleware that will read the hostname that nginx passes to it from Context and allow my handlers to know what subdomain is being request and return the proper data and cookies for said subdomain.

It's a pretty simple setup and it seems to work fine from my test in postman as all my routes are the same across all my subdomains so this way i can only use one router for all of them instead of one router per subodmain.

Now my big problem come when i'm trying to do end to end testing.

I'm setting up my test like this :

I'm trying to follow this get started guide to make an access token request. It provides a bash script as an example of how to do that. Another requirement is to make this call from Azure Function, so I've created an HTTP triggered Azure Function project in Visual Studio 2019.

It consists of 4 parts:

1. Loading certificates
2. Computing digest
3. Generating signature
4. Making a correct request to a provided API endpoint

There are two certificates provided as key pairs in .cer and .key files. One is to authenticate a request, another to create a signature with. I've combined the public and private keys into a .pfx container with openssl command like so:

It's my first time playing with Oracle Cloud (or any cloud for that matter) and I'm doing a self-learning exercise where I've created an Angular application (not AngularJS) and I want to upload images in my Oracle Cloud Object Storage Bucket. I'm working on the assumption that what I'm trying to achieve is possible with only Angular (i.e: no mid-tier is required, like PHP, C#, Java, etc).

I'm at the point where I need to create the "authorization" header that is (to my understanding) used to authenticate the PUT request, and I'm unable to get this working. From what I understand reading the Request Signature documentation, it appears that I might not actually be able to do it purely in Angular and that some sort of mid-tier would be necessary, as the documentation shows only code examples for mid-tier technologies.

What I'd like to know is it even technically possible to call the Oracle Cloud Object Storage API with only a front-end framework like Angular? I've tried using CryptoJS and using something like HmacSHA256 to generate the signature, but every time the API call is executed, Oracle Cloud constantly recevie the following error: