Kiran Apex yana fita daga Salesforce, ba daga VPN ɗinka ba
VPN a kwamfutar tafi-da-gida yana ba burauzarka hanya, ba Apex ko Marketing Cloud ba. Haɗa ainihin mai kira da ƙofar jama'a ko ingantacciyar hanyar sirri.
API na sirri yana amsa a burauzarka da zarar kwamfutar ta shiga VPN, don haka ya kamata haɗin gwiwar ya yi aiki. Ba ya aiki, domin lambar da ke yin kiran tana gudana a wani wuri daban gaba ɗaya. Apex yana gudana a sabar aikace-aikace na Salesforce, kuma aikin gefen sabar a Marketing Cloud yana gudana a cikin yanayin gudanar da wannan samfurin. Babu ɗayansu da ke gado ramin kwamfutarka. Yi wannan a matsayin ɗan gajeren tsari: gano mai kira, zaɓi ƙofar da mai kiran zai iya isa, haɗa hanyar daga farko zuwa ƙarshe, sannan tabbatar daga yanayin gudanarwa kansa.
Rubuta katin mai kira kafin duk wani canjin cibiyar sadarwa
Cika filaye biyar kuma ka ƙi yin hasashen kowane ɗayansu. Samfurin gudanarwa da mahallin suna yanke shawara kan duk abin da ke gaba, don haka fara daga nan ba daga bangon wuta na sabar ba.
| Field | What it must answer |
|---|---|
| Runtime | Which product and execution context issues the request? |
| Endpoint | Which hostname must that runtime resolve, and to what? |
| Path | Which supported public entry or private connection carries it? |
| Identity | Which credential and which operation is the API asked to authorize? |
| Failure | How do responses return, and what happens when the path is down? |
Shafin burauza da kiran Apex abokan ciniki ne daban-daban, kuma burauza mai aiki yana tabbatar da cewa akwai hanya daga teburinka kawai. Idan filin yanayin gudanarwa ya ce Apex, tambayar da ta dace ita ce daga waɗanne adireshi Salesforce ke fita, ba waɗanne adireshi kwamfutarka ke da su ba. Shi ya sa ramin da ke sa API ɗin lodawa a burauza zai iya barin haɗin gwiwar ya gaza da lokacin jira iri ɗaya da da. Katin mai kira yana nan don hana wannan kuskure kafin wani ya gyara bangon wuta.
Zaɓi ƙofar da mai kiran zai iya amfani da ita da gaske
Dukansu zane-zane sun halatta, kuma suna magance matsaloli daban-daban. Na farko ƙofa ce ta jama'a da gangan: ƙofar API ta HTTPS ko sabis ɗin haɗin kai wanda ke tabbatar da mai kira, yana amfani da ƙananan izini, kuma yana riƙe da haɗin da aka kare zuwa bayanan baya na sirri. Wannan ba daidai yake da fallasa kowane sabis na baya ko tura tashar sarrafawa zuwa intanet ba.
Na biyu ingantacciyar hanyar sirri ce. takardun Private Connect na waje na Salesforce sun bayyana yadda ake tura kiran da aka goyi baya ta hanyar Outbound Network Connection da ke da alaƙa da shaidar da aka ambata, bisa tsarin AWS PrivateLink da aka ayyana. Fasalin yana da iyakoki na bugu, lasisi da samfur, don haka tabbatar da ƙungiyar ta cancanta kafin yin zane a kansa.
Babu ɗayan zanen da ke zama abokin ciniki na OpenVPN da aka shigar cikin Salesforce, kuma tsohuwar maganar cewa kowane haɗin gwiwa dole ya isa bayanan baya na jama'a ta yi yawa a duk inda ingantacciyar hanyar sirri ta dace. Zaɓi wanda yanayin gudanarwa ke goyan bayansa, sannan kammala hanyar zuwa ainihin API: ƙarshen AWS bai san albarkatinka na gida ba kuma bai gaji hanyar kwamfutarka ba. DNS, tura bayanan baya, manufar shiga da zirga-zirgar amsa duk dole ne su bi gine-ginen da ka zaɓa. Hanyar sirri da aka gina rabin-rabin tana gaza ta yadda za ta yi kama da matsalar tabbatarwa.
Haɗa hanyar sirri daga farko zuwa ƙarshe
Yi aiki daga API zuwa waje kuma tsaya a rami na farko. Tabbatar da bayanan baya suna amsa a gida, sannan ƙarshen sirri ya isa gare su, sannan shaidar da aka ambata da haɗin waje nata suna nufin wannan ƙarshen.
curl -sS -m 5 -o /dev/null -w '%{http_code}\n' http://10.40.8.20:8080/health
dig +short api.partner.example
sf apex run --file scripts/apex/callout-check.apex --target-org integrationUmarni na farko yana tabbatar da bayanan baya suna da lafiya daga cikin hanyar sadarwar sirri, na biyu yana nuna abin da sunan ke warwarewa, kuma na uku yana aiwatar da kira daga ainihin yanayin gudanarwa na Salesforce. 200 daga na farko da gazawa daga na uku suna keɓe ramin zuwa hanyar ko shaidar, ba zuwa sabis ɗin ba.
Riƙe iyakar asalin daidai yayin da kake haɗawa. Shaidar da aka ambata ba ta gyara ƙarshen da ba za a iya isa ba da kanta, domin shaidar da haɗin sirri saitunan da ke da alaƙa ne da ayyuka daban-daban. Jerin IP da aka yarda yana taƙaita shigar cibiyar sadarwa kuma ba shaidar API ba ce, don haka riƙe tabbatarwar TLS ta yau da kullun da tsarin tabbatarwa da jujjuyawar sabis ɗin kansa. Idan gwaji ya yi nasara bayan ka kashe duba takardar shaidar kawai, ka sami matsalar sunan uwar gida ne ba matsalar hanya ba, kuma takardar shaidar har yanzu tana buƙatar dacewa.
Tabbatar daga yanayin gudanarwa, sannan rubuta komawa
Karɓi buƙatun da aka yarda marar lahani daga yanayin gudanarwar haɗin kai, ba daga injinka ba. Rubuta tushen da sabis ɗin karɓa ya gani, shaidar da aka tabbatar, sakamakon, da buƙata ɗaya da aka ƙi da gangan wadda dole ta gaza.
curl -sS -o /dev/null -w '%{http_code} %{remote_ip}\n' https://api.partner.example/v1/ping
curl -sS -o /dev/null -w '%{http_code}\n' -H 'Authorization: Bearer invalid' https://api.partner.example/v1/pingGudanar da binciken biyu ɗin daga hanyar sadarwar bayanan baya kanta domin a kwatanta tushen da aka gani da abin da yanayin gudanarwa ya samar. 200 sannan 401 ko 403 shine siffar da kake so; 200 biyu suna nufin ba a aiwatar da hanyar ƙi da gaske.
Rubuta komawa kafin ka buƙace ta: wace shigarwa ta jerin yarda, shaidar da aka ambata ko haɗin waje ka canza, wa ya mallake ta, da yadda za a dawo da ƙimar da ta gabata. Sannan rufe da'irar ta hanyar ambaton mai kiran girgije da cikakkiyar hanyar sabis a cikin tikitin, domin kada wani ya sake buɗe wannan batun a matsayin matsalar VPN.