Backend resource · STATIC DECLARATIONS

MFALogin API reference · mansoq-core

Static source contract for MFALogin: 1 declared or inherited operation mappings, schema/field evidence and authorization/refusal references. Deployment and behavioral review remain explicit.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Declared route and availability

This resource is declared in mansoq-core at /api/v1/mfa/. verified core mount in config/urls.py A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

Method	Path	Action	Evidence
POST	`/api/v1/mfa/login/`	login	@action declaration

login · POST

POST /api/v1/mfa/login/ — action login. static contract extracted; runtime/permission/payload behavior review pending.

decorator request: MFALoginRequest. Declared fields below; inherited fields are retained in the schema inventory.

Field	Type	Required	Constraints
method	LoginMethod	true	No extra constraint extracted
code	str	true	No extra constraint extracted
temp_token	str	true	No extra constraint extracted

decorator responses: MFALoginResponse. Declared fields below; inherited fields are retained in the schema inventory.

Field	Type	Required	Constraints
access	str	true	No extra constraint extracted
refresh	str	true	No extra constraint extracted

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Declared refusal/error evidence: ValidationError: Invalid login method; ValidationError: Invalid TOTP code; ValidationError: Invalid or already used backup code.

Direct refusal present: the handler/helper contains a top-level raise. Review whether the operation is intentionally disabled or only performs validation before relying on it.

Integration review checklist

Confirm the installed route and full schema; review authentication, organization/facility scoping, all accepted fields, value-state and date/time semantics, idempotency, pagination, response/exception branches and the allowed correction/reversal workflow. Test positive and negative cases with synthetic data. This source reference does not establish external certification or replace an illustrated user procedure.

Pinned source evidence

Links require access to the private source repository.