These credentials are validated by POST /backoffice/authenticate.
Flow A uses username+password; Flow B uses a token (OTP).
Username / Password — Flow A
Username
Password
User ID (SOF)
OTP Tokens — Flow B
SOF generates these and passes them to the client for SSO. The mock validates them directly.
Token
User ID
Username
Test Scenarios
Global
Per-contract status overrides
Override what GET /contracts/{id}/status returns.
The stored contract is not modified — this only affects the status polling response.
Keys are contract IDs (strings). Supported fields:
status,
amount_offer,
installments_count_offer,
external_url,
rejection_reason,
is_ready_to_sign_agreement,
is_ready_to_disburse.
scenarios.contracts
Request Loglive
Time
Method
Path
Status
No requests yet
RabbitMQ
RabbitMQ:checking…queues: agents · users
agents queue
Simulates SOF pushing agent-related events. The app's
QueueConsumerAgents worker picks them up.
Set RABBITMQ_URL=amqp://guest:guest@localhost:5672 to connect.
Entity payload — select an existing entity or edit the JSON directly