CCloudflare Docs
Use Cloudflare public key infrastructure (PKI) to create client certificates and enforce mutual Transport Layer Security (mTLS) encryption.
Athanks i implemented it and its working fine.. one last think its working for example.com but not api.example.com and i saw this.. is there any solution for it so that it work on subdomain?
Ado i will need to create certs locally?
CIt should work fine as long as the certificate match
MNote that * wildcards are not supported, the api.example.com domain will probably require its own cert or re-create your existing cert to include api subdomain 
Afor this you mean adding api.example.com in SSL/TSL -> Origion Certificate or SSL/TSL -> Edge Certificates ????
Mthe cert on your origin, where api resolves to
Mif it's SSL protected by the wildcard, *.example.com thats probably the issue, needs to be explicitlly set api.example.com
api.example.comAi removed * one and added api.example.com, regenerated cliente cert and followed all steps but its not accessible with or without certificate
Mtried again with a hard refresh? CTRL Shift R?
Ai am testing it with python requests library
Ait was working for example.com
Abut not for subdomain
MOoh if you visit the domain in a browser, what does the SSL cert tell you? valid?
Ayes app is working fine with ssl, but when i activate WAF rule it is not accessible
Mis it for *.example.com or the api.example.com the cert viewed from browser?
Ait saying example.com
MMy CF proxied records for example will still display: even with custom SSL certs on my origin. But i don't want you to un-proxy the record either. I hope there's a way to generate custom certs, probably with the custom cert manager on Cloudflare
Mfor the url api.example.com cert only for example.com?
Ai have DM you the url...
Ahere is a working example for domain example.com with and without client certificate
Abut samething is not working in case of subdomain abc.example.com
