How to pass SSL Certificate with Swagger UI from Angular 4 when invoking a REST API
Hello, I have a query. How to pass SSL Certificate with Swagger UI from Angular 4 to invoke a REST API , which is enabled with Mutual Authentication via certificate? Do we have any provision to intercept the request in Swagger UI before invoking a particular API request. My Application Ex: My application(A) is getting the Swagger JSON from the bitbucket of another target application(B) and rendering it in my application(A) with Swagger UI. Now the target application(B), has enabled Mutual Auth. Now when the API of application(B) is invoked from the Swagger UI of my application(A), how can we pass the SSL Certificate along with this API call? I would also like to know what other approach(es) can be used to pass Authentication when trying out any API?Status": "TH99401: Invalid Client Certificate
Hello Team , We have recently bought an SSL certificate and implemented it in our AWS environment. We can observe that the SSL certificate is already been imported successfully "https://decoder.link/sslchecker/athos-api-uat.happy-tech.in/443". Our main purpose to buy the certificate was to make 2-way handshaking with one of our partners however when we do it we get failure. Steps we did:- -Configured certificate into our Aws Load balancer. -Checked "https://decoder.link/sslchecker/" and our https works fine -Hit the API from our server to our partner with body and got the below error. HTTP/1.1 401 Unauthorized Content-Type: application/json;charset=UTF-8 Content-Length: 276 Date: Fri, 16 Oct 2020 11:30:16 GMT Server: myServer { "RequestEncryptedValue": "", "RequestDigitalSignatureValue": "", "SessionEncryptedValue": "", "SessionDigitalSignatureValue": "", "Source": "Happy_Lead", "TransactionId": "2018-10-11T15:04:14.900+05:30", "Status": "TH99401: Invalid Client Certificate" } - Just to narrow down our problem, we installed SOAP UI and tried to hit the API with Keystore(our private key in .p12 format) and trust store (our partner's public key). - We got the same error, so to further narrow down, we generated a self-signed SSL certificate and tried with that, and it got a success . What can we check next?Solved2.5KViews0likes4Comments