Summary:
Basware is now introducing mandatory multi-factor authentication (2-step verification) for Basware Portal customer and supplier users.
Integration is being done with Basware Access and Authsignal supporting verification methods (Email OTP and Passkeys).
Local username/password sign-in will be replaced with verified email-based authentication via Basware Access.
Logging in using only a legacy username/password will no longer be allowed. User accounts are migrated so that the primary identifier is a verified email address, and authentication tokens (JWT cookies) issued by Basware Access track whether MFA has been successfully completed.
Implementing MFA protects sensitive supply chain and financial data against credential theft, credential stuffing, and unauthorized access.
Enforces buyer-mandated security requirements for accessing sensitive purchase orders, invoices, and documents.
Centralizes identity management and session validation across the Basware Network.
Implementation Schedule:
Pre-Production Deployment: 12th November 2026
Production Deployment: 25th November 2026
How MFA Is Integrated and Managed by Basware
Portal Role: Serves as the primary entry point where users initiate the "Enable MFA" flow or are prompted via in-app banners/document access gates.
Basware Access Role: Acts as the central identity provider handling MFA registration, ongoing method management (Email), and MFA deactivation.
Portal UI Options:
Users without MFA see "Enable MFA" on their Account page.
Users with active MFA see a "Modify MFA" redirect link to Basware Access. (Disabling MFA is managed in Basware Access, not locally within the Portal).
How User Migration Is Handled
Existing Users:
User clicks Enable MFA on the Portal Account page.
Confirmation prompt informs the user that enabling MFA resets their local password and sends an activation email.
An asynchronous API call creates/migrates the user in Basware Access, setting status to MFA activation in progress.
User follows the email link, resets password, and registers their MFA method in Basware Access.
Upon signing in, a valid JWT cookie is issued, local Portal passwords are removed, and migration is finalized.
New Users: Enrolled automatically in Basware Access with MFA setup during initial registration.
Potential Issues Customers Can Face
Shared/Generic Email Accounts: Multiple users sharing an email address cannot enroll independently until assigned unique emails.
Asynchronous Activation Delays: Users leaving the flow incomplete remain stuck in "MFA activation in progress", temporarily blocking access to protected documents.
Legacy Username Confusion: Attempting to log in using legacy portal usernames instead of their verified primary email.
Session & Cookie Issues: Multi-tenant simultaneous sessions in the same browser window can cause session conflicts.
Surprise Regarding Password Reset: Users being unaware that starting MFA migration invalidates their local portal password.
What to Do If Customers Report an Issue with MFA
Diagnostic Checklist: Determine whether the user is new vs. existing, whether the email setup link was opened and completed, and what specific action is failing.
Triage & Resolution Guidance:
Cannot enable / missing link: Check account status in MDD/Portal and verify email uniqueness.
Stuck in "Activation in Progress": Have the user check their inbox/spam for the Basware Access reset link and complete the flow.
Wants to modify/disable MFA: Direct the user to their Basware Access account page via the "Modify MFA" link.
For any other issue, a task can be raised to support engineers.