Feature Request: Streamline SSO + 2FA Sign-Off Process for Safety Reports

Problem Statement

Users with Single Sign-On (SSO) and Two-Factor Authentication (2FA) enabled experience significant friction when signing off on safety reports within Vellox. The current implementation requires full re-authentication—including SSO credential entry and 2FA challenge completion—for each sign-off action, even within active sessions. This creates unnecessary delays and frustration for routine, time-sensitive safety report workflows.

Current Behaviour

When a user attempts to sign off on a safety report with SSO + 2FA enabled, the system:

1. Redirects the user to the SSO authentication page

2. Requires full credential entry (username/password or identity provider login)

3. Triggers a 2FA challenge (SMS code, authenticator app, or hardware token)

4. Returns the user to the report sign-off page after successful authentication

5. Completes the sign-off action

This full authentication cycle occurs even when the user has an active authenticated session and may have authenticated recently (within minutes or hours).

Time Impact: Each sign-off requires 30-90 seconds of additional authentication overhead, depending on 2FA method and network conditions.

Enhancement: Authentication

• Recognise the sign-off action

Technical Implementation

• Leverage existing session tokens with extended validation

• Introduce a "last_authenticated" timestamp in session metadata

• Add configurable policy controls for administrators:

  • Trust window duration

  • Organisational override for compliance requirements