- Shipped
- 15 Novemba 2026, 04:50 UTC
- Author
- Kamo
- Commit
- f04e606
Mfano: 200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 (ya umma, discoverable tu - allowCredentials daima tupu), GET/PATCH/DELETE /api/security/passkeys. RP ID = mzazi wa sherehe mwenyeji (login.acme.com -> acme.com), kuhifadhiwa katika user_passkeys.rp_id; residentKey + userVerification Inahitajika hivyo passkey NI sababu ya pili; changamoto moja-kutumia (PKREG/PKAUTH GETDEL, 5 min); saini counter kwenda nyuma = PASSKEY_SUSPECT (kuchunguzwa HIGH, mstari kuhifadhiwa). PASSKEY_ADDED / kuondolewa + barua, LOGIN_PASSKEY. Barua pepe kanuni (org email_code_enabled): signin / barua pepe-kanuni / kutuma | kuthibitisha - jibu sawa kwa kila kitambulisho, barua kutumwa async tu kwa ajili ya akaunti halisi kuruhusu org wanaweza kukubali, 6 namba, 10 min, 5 majaribio, kuweka nyuma juu ya makosa yetu wenyewe. Sababu moja; LOGIN_EMAIL_CODE . Mtazamaji wa kuaminika (org trusted_device_days): mfa / changamoto kukumbukaDevice -> trustedDeviceToken; X-Kamo-Trusted-Kifaa kichwa skips tu hatua authenticator (password kuingia + SignInCompletion); kusahau juu ya mabadiliko yoyote ya nywila na kujiunga-out-wote. KamoMobile idhini: **************** idadi kulinganisha (2 nambari juu ya kompyuta, 3 chaguzi juu ya simu, moja mbaya kuchagua kukana), 2 min, kushinikiza kama SIGNIN_APPROVAL kupitia MediaService; QR: signin/qr/start|status + kifaa qr-preview|qr-approved, mkutano ardhi katika org simu alichagua. kifaa mwisho pointi authenticated na X-Kamo-Kifaa-Token (kuthibitishwa, si kuzunguka). signin / mbinu sasa majibu **************** kutoka sera + kuua swichi. **************** anaendesha kila mlango chini (akaunti, nafasi ya kazi, njia ya org swichi, sheria ya upatikanaji, SignInCompletionService) trusted-kifaa header ni kutumwa.