Sebenzisa i-transport eyodwa ye-proxy ye-Firebase Admin Java nokuvuselelwa kwethokheni

Dlulisa i-transport factory ku-GoogleCredentials kanye ne-transport ku-FirebaseOptions ukuze zombili izindlela ze-HTTP zithole i-proxy.

Hlela kokubili okokufaka kwe-transport lapho izingcingo ze-HTTP ze-Firebase nokuvuselelwa kobufakazi kufanele kusebenzise i-proxy efanayo. Indawo yokugcina ye-HTTP yomphakathi ekhethwe uhlu lwe-proxy ye-HTTP idinga lezi zinto ezimbili zokudlulisa:

var proxy = new java.net.Proxy(
    java.net.Proxy.Type.HTTP,
    new java.net.InetSocketAddress("proxy.example.net", 8080));

var transport =
    new com.google.api.client.http.javanet.NetHttpTransport.Builder()
        .setProxy(proxy)
        .build();

var credentials = com.google.auth.oauth2.GoogleCredentials.fromStream(
    serviceAccountStream, () -> transport);

var options = com.google.firebase.FirebaseOptions.builder()
    .setCredentials(credentials)
    .setHttpTransport(transport)
    .build();

var app = com.google.firebase.FirebaseApp.initializeApp(options);

Ukudlulisa okubili okubalulekile i-fromStream(serviceAccountStream, () -> transport) kanye ne-setHttpTransport(transport). Okokuqala kunikeza i-transport ye-HTTP yokuthola amathokheni okufinyelela; okwesibili kunikeza i-transport ye-HTTP yohlelo lokusebenza lwe-Firebase. Uma kubekwa okukodwa kuphela, okunye kungase kuhlale emzileni wako wokuzenzakalela.

serviceAccountStream iwukugeleza kobufakazi be-akhawunti yesevisi ethembekile yohlelo. Gcina uhlelo lomsebenzi walo futhi luyekele ngomjikelezo ojwayelekile wempilo ye-Firebase. Isilungiselelo se-proxy sishiya igama lomsingathi wendawo yokufika lingashintshiwe ukuze kuqinisekiswe i-TLS; asidingi ukushintshwa kwekilasi le-SDK noma i-SSL factory ethemba konke.

Ububanzi lapha yizindawo zokuxhumana ze-HTTP ezikhonjisiwe. Umsebenzi osebenzisa i-Realtime Database WebSocket noma enye i-transport yesevisi udinga ukusekelwa kokuqondisa kwaleyo transport kuhlolwe ngokwehlukana.

Izihloko ezihlobene