I-REST Assured inencazelo ye-proxy ethwala ikheli nemininingwane yokuqinisekisa ye-proxy ndawonye:

import static io.restassured.RestAssured.given;
import io.restassured.specification.ProxySpecification;

var proxy = ProxySpecification.host("proxy.example")
    .withPort(8080)
    .withScheme("http")
    .withAuth(proxyUser, proxyPassword);

var request = given().proxy(proxy);

Uhlelo lunikeza i-proxyUser ne-proxyPassword kusuka emthonjeni wayo ojwayelekile wemininingwane yokuqinisekisa. Le ngxenye yakha incazelo yesicelo; shaya i-URL ye-API ehlosiwe nge-request usebenzisa ikhodi ejwayelekile yesicelo nokuhlola yokuhlolwa.

Uhlelo lwe-http luchaza iphuzu lokugcina le-proxy. I-URL ye-API ingahlala iyi-HTTPS. Indlela ye-withAuth ye-REST Assured inikeza ukuqinisekiswa kwe-proxy okuyisisekelo; ayixoxisani nazo zonke izinhlelo zokuqinisekisa zebhizinisi ngenxa nje yokuthi kunikezwe izintambo ezimbili.

Beka imininingwane yokuqinisekisa ye-API ekuhlelweni kwayo kokuqinisekisa. Gwema ukushintsha i-akhawunti ye-proxy ngesihloko esijwayelekile se-Authorization noma ngephasiwedi yesevisi. Ku-HTTPS, ukuqinisekiswa nomlamuli kungadingeka lapho kusungulwa i-CONNECT, ngaphambi kokuba ukushintshana kwe-HTTP nendawo ekuyiwa kuyo kube khona.

Lapho ukwehluleka okusele kuwukwethemba isitifiketi

Inselelo ye-CONNECT enqatshiwe ne-phutha lokuqinisekisa isitifiketi se-TLS kuyimiphumela ehlukene. Uma i-CA edingekayo ephethwe yinhlangano ingekho ekuhlelweni kokwethemba kweklayenti, thola leyo CA ngomzila wokuphatha ogunyaziwe bese uhlela i-truststore yeklayenti lokuhlola.

I-REST Assured iveza i-trustStore ngale njongo. I-truststore ishintsha ukuthi iklayenti ye-HTTPS ithemba abakhiphiphi; ayikhethi i-proxy futhi ayinikezi ukungena kwayo. Gcina ukuqinisekiswa kwegama lomsingathi nesitifiketi kuvuliwe esikhundleni sokusebenzisa ukuxhawana kwe-accept-all ukwamukela noma yisiphi isitifiketi esethulwayo.

Izihloko ezihlobene