401 Incorrect credentials with mutual ssl helloworld endpoint test

[asrini]

Hi I am trying to test mutual ssl connection with hello world example in the sandbox provision and I am getting a 401 with incorrect credentials. I used the auto-generate csr option and followed the example exactly as stated so I am not sure what is going on here. I know the username and password found in the credentials tab is correct. I tried with SoapUI and Postman as well. I am also not able to upload my manually generated csr.  Visa returns an error and doesn't say why.  Please help. Relevant info below. 

HTTP/1.1 401
Server: nginx
Date: Thu, 26 Sep 2024 02:24:20 GMT
Content-Type: application/json
Content-Length: 119
Connection: keep-alive
X-SERVED-BY: -576878785
X-CORRELATION-ID: 1727317460_228_1931013393_-576878785_VDP_WS
x-vdp-normalized-url: /vdp/helloworld
X-APP-STATUS: 401
x-vdp-authn-api-visa-id: HELLOWORLD
X-ERROR-ORIGIN: 9100

{"responseStatus":{"status":401,"code":"9124","severity":"ERROR","message":"Incorrect credentials supplied","info":""}}

[SyedSa]

Hi @asrini, Thank you for reaching out. An agent will get back to you as soon as possible. Until then, if any community member has information that may be helpful, please feel free to reply.

[asrini]

Update, I was able to generate my own csr and upload it to visa. The problem was the common name not being a "domain name i.e. example.com". However after obtaining the new set of credentials and trying my luck again with Postman and SoapUI, I am still getting a 401 error but the message is different. Now in SoapUI it says authentication failed instead of incorrect credentials. Please advise.  The new request details are below: 

HTTP/1.1 401
Server: nginx
Date: Sat, 28 Sep 2024 18:36:13 GMT
Content-Type: application/json
Content-Length: 110
Connection: keep-alive
X-SERVED-BY: -6979957788d9c
X-CORRELATION-ID: 1727548573_330_497203810_-6979957788d9c_VDP_WS
x-vdp-normalized-url: /vdp/helloworld
X-APP-STATUS: 401
x-vdp-authn-api-visa-id: HELLOWORLD
X-ERROR-ORIGIN: 9100
X-Frame-Options: SAMEORIGIN

{"responseStatus":{"status":401,"code":"9125","severity":"ERROR","message":"Authentication failed","info":""}}

Is it still because of the common name? Does visa actually check this?