Isirekhodi se-JMeter esithenjwayo sisadinga ukhiye weklayenti we-mTLS
I-CA yokurekhoda ivumela isiphequluli ukuthi sithembe i-JMeter; ukuxhumana kwe-HTTPS okuqhubekayo kwe-JMeter kudinga isitifiketi seklayenti esigunyaziwe kanye nokhiye oyimfihlo wohlelo.
Ukufaka i-CA yokurekhoda ye-JMeter esipheqululini kuxazulula uhlangothi olulodwa lokuthemba: isiphequluli singamukela izitifiketi zewebhusayithi ezishintshwe isirekhodi. Akunikezi i-JMeter ukhiye oyimfihlo weklayenti wokuxoxisana kwe-mTLS kohlelo.
browser → JMeter recorder → mTLS application
records HTTPS presents client identityEkurekhodweni okuvinjiwe, i-JMeter yiyo eyenza lokho kuxhumana kwe-HTTPS okuqhubekayo. Khetha isitifiketi seklayenti esigunyaziwe nokhiye oyimfihlo ohambisanayo kusuka ku-JKS noma i-PKCS12 keystore ngokusebenzisa Options → SSL Manager, noma ukulungiselelwa kwe-JVM keystore okubhaliwe. Cabangela ukusetshenziswa kwe-HTTP nokukhethwa kwe-alias okusetshenziswa ukuhlola. Isitifiketi se-CA esivamile sodwa asikwazi ukunikeza lowo mazisi.
Hlola ukushintshana ngokulandelana: ukuthemba kwesiphequluli kwisirekhodi, noma yikuphi ukuxhumana nokuqinisekiswa kwe-proxy yenkampani, bese kuba ukuxoxisana kwe-TLS nendawo okuyiwa kuyo. 407 ingeyokungena ku-proxy; ukushintsha isitifiketi se-mTLS akukwazi ukukuxazulula.
Idatha yezicelo erekhodiwe ayithwali ubunikazi bokhiye oyimfihlo ekudlaleni kabusha kwakamuva. Iklayenti eliphumayo lokudlala kabusha nalo lidinga ukulungiselelwa kobunikazi okusebenzayo. Uma ukudlala kabusha kuthola i-407 ku-proxy, lungiselela ngokwehlukana izifakazelo ze-proxy eziphumayo ze-JMeter.