Wicitaannada Apex waxay ka baxaan Salesforce, ma aha VPN-kaaga
VPN-ka kombiyuutarka guud wuxuu browser-kaaga siinayaa waddo, ma aha Apex ama Marketing Cloud. U eeg wicitaanka dhabta ah shaybaadhka guud ama isku xirka gaarka ah ee u qalma.
API-ga gaarka ah wuxuu ka jawaabaa browser-kaaga isla marka uu kombiyuutarku ku biiro VPN-ka, sidaas darteed isku-xirku waa inuu shaqeeyaa. Ma shaqeeyo, sababtoo ah koodhka sameeya wicitaanku wuxuu ku socdaa meel kale gebi ahaan. Apex wuxuu ku socdaa server-yada codsiga Salesforce, iyo hawsha dhinaca server-ka ee Marketing Cloud waxay ku socotaa runtime-ka badeecadaas. Midkoodna ma dhaxlo tunnel-ka kombiyuutarkaaga. U samee sidan oo kale oo ah nidaam gaaban: aqoonsado wicitaanka, dooro irrid uu wicitaanku gaari karo, isku xir waddada bilow ilaa dhammaad, ka dibna ka xaqiiji runtime-ka laftiisa.
Qor kaadhka wicitaanka ka hor isbeddel kasta oo shabakadeed
Buuxi shan goobood oo diid inaad midkoodna qiyaasto. Badeecada fulinta iyo macnaha ayaa go'aamiya wax kasta oo xiga, marka ka bilow halkaas halkii aad ka bilaabi lahayd firewall-ka server-ka.
| 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? |
Tab browser iyo wicitaan Apex waa laba macmiil oo kala duwan, browser shaqeeya wuxuu kaliya caddeeyaa in waddo ka timaado miiskaaga. Haddii goobta runtime-ku tidhaahdo Apex, su'aasha habboon waa adressyada ay Salesforce ka baxdo, ma aha adressyada kombiyuutarkaagu leeyahay. Taasi waa sababta tunnel-ka API-ga browser-ka u rarta uu isku-xirka uga tagi karo isla waqtigaas hore. Kaadhka wicitaanku wuxuu u jiraa inuu joojiyo qaladkaas ka hor inta aan qof firewall wax ka beddelin.
Dooro irridda uu wicitaanku dhab ahaan isticmaali karo
Laba naqshadoodba waa sharci, waxayna xalliyaan mashaakil kala duwan. Midda koowaad waa irrid guud oo ula kac ah: irrid API HTTPS ama adeeg isku-xir oo xaqiijiya wicitaanka, ku dhaqma fasaxyo cidhiidhi ah oo haysta xiriir la ilaaliyay backend-ka gaarka ah. Taasi la mid ma aha in la soo bandhigo adeeg kasta oo backend ah ama deked maamul loo gudbiyo internet-ka.
Midda labaad waa isku xir gaar ah oo u qalma. Dukumeentiga Private Connect ee baxa ee Salesforce wuxuu sharraxayaa jihaynta wicitaannada la taageeray iyada oo loo marayo Outbound Network Connection oo ku xiran aqoonsi magac leh, iyada oo loo marayo habaynta AWS PrivateLink ee qeexan. Astaantu waxay leedahay xaddidaadyo daabacaad, shati iyo badeecad, marka xaqiiji in hay'adda u qalanto ka hor inta aanad naqshadayn agagaarkeeda.
Midkoodna naqshadaynta ma aha macmiil OpenVPN lagu rakibay gudaha Salesforce, iyo sheegashada hore ee ah in isku-xir kastaa gaaro backend guud waa mid aad u ballaaran meel kasta oo isku xir gaar ah oo la taageeray ku habboon yahay. Dooro midda runtime-ku taageerayo, ka dibna dhammaystir waddada ilaa API-ga dhabta ah: barta AWS ma aqoonsato kheyraadkaaga maxalliga ah mana dhaxlo waddada kombiyuutarkaaga. DNS, jihaynta backend, siyaasadda gelitaanka iyo taraafikada jawaabta dhammaantood waa inay raacaan dhismaha aad dooratay. Waddo gaar ah oo badh dhisan waxay ku guuldareysataa si u eg si sax ah dhibaatada xaqiijinta.
Isku xir waddada gaarka ah bilow ilaa dhammaad
Ka shaqee API-ga dibadda oo joogso marka hore ee bannaan. Xaqiiji in backend-ku maxalli ahaan u jawaabo, ka dibna in barta gaarka ah ay gaarto, ka dibna in aqoonsiga magac leh iyo xiriirkiisa baxa ay bartilmaameedsadaan bartaas.
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 integrationAmarka koowaad wuxuu caddeeyaa in backend-ku caafimaad qabo gudaha shabakada gaarka ah, tan labaad waxay tusaysaa waxa magacu u xalliyo, tan saddexaadna waxay fulisaa wicitaan ka imanaya runtime-ka dhabta ah ee Salesforce. 200 ka imanaya tan koowaad iyo guuldarro ka imanaysa tan saddexaad waxay go'doomiyaan bannaanida waddada ama aqoonsiga, ma aha adeegga.
Hayso baaxadda aqoonsiga oo sax ah inta aad isku xirayso. Aqoonsi magac leh kaligiis ma hagaajiyo barta aan la gaari karin, sababtoo ah aqoonsiga iyo isku xirka gaarku waa dejinta xiriir leh oo leh hawlo kala duwan. Liiska IP ee la ogolaaday wuxuu cidhiidhiyaa gelitaanka shabakada mana aha aqoonsi API, marka hayso xaqiijinta TLS caadiga ah iyo habka aqoonsiga iyo wareegga adeegga laftiisa. Haddii tijaabadu ay kaliya gudubto ka dib markaad damiso hubinta shahaadada, waxaad heshay dhibaato magac martigeliyaha ah ee ma aha waddo, shahaadaduna wali waa inay u dhiganto.
Ka xaqiiji runtime-ka, ka dibna qor dib-u-noqoshada
Aqbal codsi la ogolaaday oo aan waxyeello lahayn oo ka imanaya runtime-ka isku-xirka, ma aha mashiinkaaga. Qor isha la arkay ee adeegga qaata, aqoonsiga la xaqiijiyay, natiijada iyo hal codsi si ula kac ah loo diiday oo ay tahay inuu guuldareysto.
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/pingKu socodsii labada baaritaan isla shabakada backend-ka laftiisa si isha la arkay loo barbardhigo waxa runtime-ku soo saaray. 200 oo ay ku xigto 401 ama 403 waa qaabka aad rabto; laba 200 waxay ka dhigan tahay in waddada diidmada aan dhab ahaan la dhaqangelin.
Qor dib-u-noqoshada ka hor inta aanad u baahnayn: goobta liiska ogolaanshaha, aqoonsiga magac leh ama xiriirka baxa ee aad beddeshay, yaa leh iyo sida loo soo celiyo qiimihii hore. Ka dib xir wareegga adigoo ku sheegaya tikit-ka wicitaanka daruuraha iyo waddada buuxda ee adeegga, si aanay qofna mar kale u furin isla arrintaas dhibaato VPN ahaan.