Soo-dejiyaha key-set-ka fog ee jose4j wuxuu leeyahay shaykiisa soo-qaadista HTTP. Habee shaygaas marka abka uu wici karo API laakiin uusan soo dejisan karin JSON Web Keys ee soo-saaraha.

API-ga jose4j 0.9.6 wuxuu bixiyaa Get.setHttpProxy iyo HttpsJwks.setSimpleHttpGet:

org.jose4j.http.Get downloader = new org.jose4j.http.Get();
downloader.setHttpProxy(new java.net.Proxy(
    java.net.Proxy.Type.HTTP,
    new java.net.InetSocketAddress("proxy.example", 8080)));
downloader.setConnectTimeout(5000);
downloader.setReadTimeout(15000);

org.jose4j.jwk.HttpsJwks jwks = new org.jose4j.jwk.HttpsJwks(
    "https://issuer.example/keys");
jwks.setSimpleHttpGet(downloader);

Isticmaal shaygan jwks ee habaysan ee habaynta xallinta furayaasha abka. Abuuristiisa dhinaca xalliyaha jira ma beddelo instance-ka kale ee xalliyahaas.

Get wuxuu isticmaalaa URL iyo HttpsURLConnection. Proxy-ga cad waxaa loo gudbiyaa URL.openConnection(Proxy); tani waxay dariiqa ku xaddiddaa soo-dejiyahan halkii ay u baahan lahayd siyaasad proxy cusub oo JVM oo dhan ah. Aqoonsiga proxy-ga, haddii loo baahdo, waa arrin gaadiid dheeraad ah. URL soo-saare la ansixiyay oo si dadweyne loo gaari karo waxay isticmaali kartaa cinwaan HTTP ka mid ah liiska proxy-yada HTTP marka dhexdhexaadiyeyaasha dadweynaha la oggolaado oo aan akoon proxy la habayn.

HttpsJwks wuxuu keydka ku kaydiyaa furayaasha instance kasta, iyada oo ku saleysan cinwaannada keydka iyo dejinta muddada keydka ee caadiga ah. Hayso instance-ka si aad u hesho faa'iidadaas. Fure hore loo kaydiyay wuxuu u oggolaan karaa xaqiijinta inay sii socoto iyada oo aan shabakadda isticmaalin, halka soo-qaadid ama cusboonaysiin dambe ay weli ku xiran tahay dariiqa la habeeyay.

Tani waxay habaysaa soo-qaadista furayaasha. Xaqiijinta token-ka weli waxay u baahan tahay siyaasadda caadiga ah ee abka ee saxeexa, soo-saaraha, dhageystayaasha iyo hubinta kale; helista key-set JSON oo kaliya ma sameyso hubintaas.

Maqaallo la xiriira