POST/api/auth/sso/exchange

Isinyathelo sokugcina sokungena nge-SSO (SAML/OIDC): ishintshanisa ikhodi esetshenziswa kanye ekhishwe yi-Callback ibe yi-JWT yeseshini evamile.

Ikhasi elithi „POST /api/auth/sso/exchange — inkomba ye-API" liphathelene nendawo yemisebenzi eshiwo ku-URL. Okuqukethwe okukhona kwengezwa ngenqubo yangempela, izimfuneko nemikhawulo eyaziwayo. I-Zentor ayinayo isistimu yokhiye be-API bonjiniyela. Ku-dashboard kusetshenziswa ama-JWT eseshini ahlala amahora ayishumi nambili nama-refresh token ahlala izinsuku eziyisikhombisa; i-TOTP ne-SSO kungokuzikhethela. Ama-widget embed token aboniswa kanye kuphela ngombhalo ocacile futhi aboshelwe kuma-origin avunyelwe. Imibhalo ye-`POST /api/auth/sso/exchange` kufanele ifundwe ngokubophezelayo njengencazelo yobuchwepheshe yale endpoint ethile. Okubalulekile yindlela, umzila, ukuqinisekisa ubuwena, izinkambu eziyimpoqo, amaphutha angenzeka nombuzo wokuthi ukubiza futhi kuqalisa umphumela ofanayo yini. Ngakho lesi sigaba sosizo https://zentor-app.de/hilfe/api-referenz/auth/auth.sso_exchange akufanele siqukathe izitatimende zokukhangisa ezijwayelekile, kodwa kuphela izinyathelo zokuhlanganisa ezilandelekayo nezibonelo zezimpendulo ezifakazelwe. Ukuze kubizwe i-`/api/auth/sso/exchange`, isicelo sakhiwa ngokwe-registry. Imizila yomphakathi ayidingi khiye we-API wonjiniyela ojwayelekile, ngoba i-Zentor ayinikezi sistimu enjalo yokhiye. Ngakolunye uhlangothi, imizila ye-widget evikelekile isebenzisa i-embed token eboniswa kanye nokuhlolwa kwe-origin. Isimo se-HTTP nokuqukethwe kwe-JSON kufanele kuhlaziywe ndawonye; inkambu ethi `ok` iyodwa ayithathi indawo yokuphatha amaphutha. Lapho kuhlolwa i-`POST /api/auth/sso/exchange`, kufanele kusetshenziswe amanani angaziwa. Idatha yangempela yamakhasimende, ama-UUID akhiqizayo, ama-token eseshini nezitembu zesikhathi ezithile akufanele kube sezibonelweni zomphakathi. Umkhawulo owaziwayo wenkundla yonke yizicelo ezingu-2.000 phakathi kwemizuzu engu-15; umkhawulo ohlukile we-endpoint eyodwa awufakazelwe. Izingcingo ze-POST ezingeyona i-idempotent akumele ziphindwe ngokungaboni ngemva kokuphazamiseka kwenethiwekhi okungacacile. Amaphutha avamile okuhlanganisa kulo mzila avela ngenxa yemingcele eyimpoqo engekho, izinhlobo zedatha ezingalungile, amakhodi asebenza kanye aphelelwe yisikhathi, ama-origin angavunyelwe noma irekhodi elingasetshenziswanga. Uhlelo kufanele luphathe lezi zimo ngokwehlukana futhi lurekhode umlayezo wephutha obuyiswe yi-endpoint, ngaphandle kokubhala okuqukethwe okuyimfihlo. Isicelo esiphumelelayo siqinisekisa kuphela lesi sinyathelo sokucubungula, hhayi ngokuzenzakalelayo impumelelo elandelayo ye-imeyili, yenkokhelo noma ye-SSO. Lokhu kubaluleke ngqo ku-„POST /api/auth/sso/exchange". Ukuhlolwa kobuchwepheshe kwaleli khasi kufanele ngokuphoqelekile kusekelwe ku-registry ethi `app/frontend/src/content/api-reference/` nemizila ye-backend ehambisanayo. Amanothi okuhlola bukhoma angasho kuphela lokho okuhloliwe ngempela. Ukuhlola okungemuhle noma ukuqhathanisa kwekhodi akusibo ubufakazi obuphelele bempumelelo. Ngakho ku-POST /api/auth/sso/exchange — inkomba ye-API kufanele kuhlukaniswe ngokucacile phakathi kwesakhiwo esibhaliwe, ukuhlola okuzenzakalelayo nokuziphatha bukhoma okubonwe ngokuqinisekile.

{"code":"<ikhodi yokusetshenziswa kanye evela ku-SSO callback redirect>"}

{"ok":true,"token":"<JWT>","refreshToken":"<Refresh-Token>"}