Yi amfani da jigilar wakili ɗaya don Firebase Admin Java da sabunta token

Saita duka shigarwar jigila biyu a lokacin da kiran HTTP na Firebase da sabunta takardun shaida dole su yi amfani da wakili ɗaya. Ƙarshen HTTP na jama'a da aka zaɓa daga jerin wakilan HTTP yana buƙatar irin waɗannan miƙa biyu:

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);

Muhimman miƙa biyu su ne fromStream(serviceAccountStream, () -> transport) da setHttpTransport(transport). Na farko yana bayar da jigilar HTTP don samun token shiga; na biyu yana bayar da jigilar HTTP na manhajar Firebase. Saitin ɗaya kawai zai iya barin ɗayan a kan hanyarsa ta asali.

serviceAccountStream shi ne amintaccen magudanar takardun shaidar asusun sabis na manhajar. Ka riƙe manhajar don aikinta sannan ka saki ta ta hanyar tsarin rayuwar Firebase na yau da kullum. Saitin wakili yana barin sunan mahalli na makoma a tsaye don tabbatarwar TLS; baya buƙatar maye gurbin ajin SDK ko masana'antar SSL da ke amincewa da komai.

Iyakokin anan su ne mu'amalolin HTTP da aka nuna. Aikin da ke amfani da WebSocket na Realtime Database ko wata jigilar sabis yana buƙatar a duba tallafin tafiyar da wannan jigilar daban.