IBM Java SDK: saita wakilai don IAM da kiran sabis

Saita hanyoyin biyu yayin farawa, tare da mai tabbatar da IAM da aka bayar wa sabis ɗin a zahiri:

import java.net.InetSocketAddress;
import java.net.Proxy;
import com.ibm.cloud.sdk.core.http.HttpConfigOptions;

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

authenticator.setProxy(proxy);

var options = new HttpConfigOptions.Builder()
    .proxy(proxy)
    .build();
service.configureClient(options);

A nan authenticator da service su ne abubuwan da ke akwai na aikace-aikacen. Aiwatar da saitunan kafin samun token ko buƙatun sabis su fara, tare da tabbatar da takardar shaida ta yau da kullum a kunne. Inda aikace-aikacen zai iya amfani da tashar HTTP ta jama'a don duka wuraren biyu, ana samun adiresoshin da suka dace a cikin jerin wakilan HTTP.

Ayyukan biyu sun shafi buƙatu daban-daban. authenticator.setProxy yana rufe hanyar token na IAM; service.configureClient yana amfani da wakili a kan jigilar sabis. Saita ɗaya ba ya kafa hanyar ɗayan.

Idan akwai gazawa, gano masarrafar da aka ambata a cikin buƙatar da ta kasa. Samun token cikin nasara yana taƙaita matsalar ga hanyar sabis; amma ba ya tabbatar da cewa wannan hanyar ta sami zaɓuɓɓukan wakilinta.

HttpConfigOptions ya fito daga IBM Java SDK Core. Lokacin da kake daidaita tsohon misalin ConversationService, yi amfani da fakitin Core da ƙarni na sabis ɗin da aikace-aikacen ya zaɓa maimakon kwafin tsohon ajin cibiyar sadarwa na musamman na sabis.