November 20th, 2026
This release adds WhatsApp as an OTP channel for MFA, lets admins automate Apple Sign-In secrets, see who has registered which MFA method, control which FIDO2 authenticators users can register, and set the dashboard their users land on after login. It also brings webhook-based inbound provisioning and new workflow building blocks.
Admins can now enable WhatsApp as a channel for MFA one-time passcodes. miniOrange works with Meta Cloud API, 360dialog, Interakt and other BSPs, or any provider through a custom HTTP configuration. Read More.
Admins can now generate the Apple client secret automatically using the Team ID, Key ID and .p8 private key, instead of creating it manually. The Apple IDP page shows the secret's expiry status, and miniOrange sends email alerts 45, 14, and 7 days before expiry, and again after it expires, helping prevent Apple Sign-In failures. Read More.
Customer Admins and Super Admins can now open a User MFA Registration Report that shows each user's active MFA method, enrolled authentication methods, and MFA registration details.
On the new end-user dashboard, end users can choose their home page from Edit Profile > Preferences, so they can land straight on their selected home page after login. Admin users can set the same preference to open the user dashboard by default instead of the admin dashboard, which helps admins who mainly use the portal to reach their apps. Read More.
Admins can now provision users into miniOrange from external applications through a webhook in real-time. Each app gets its own webhook that can create, update, delete, enable and disable users, with support for HMAC as well as the existing authorization methods.
Admins can now provision users to and from BigCommerce through Custom Provisioning. Supported actions include creating, updating and deleting users, address updates, group creation, and bulk import of users and groups.
The TACACS+ server now supports CHAP authentication, so network devices such as Cisco Nexus switches can authenticate using CHAP. Credentials are stored securely for hash-based validation, and CHAP logins follow your existing MFA and account lockout policies.
Admins can now build offboarding workflows that run before a user is deleted. Choose On User Deletion as the trigger and pick which deletions it covers: from the admin portal, through the API, or by an external provider during provisioning.
An Approval Policy step can now be added to any workflow: pre or post user creation, pre or post user update, and user deletion.
Admins can add If / Else rules to send each user down the path that fits them. Conditions can use Identity Source, Applications or any user attribute, with operators such as equals, contains, not contains and is not present. You can combine as many conditions as you need.
Workflows can now pause and resume on their own with the new Delay step. There are three ways to wait:
User update workflows have a new Group Membership task that keeps a user’s groups in sync when their details change. Previously, admins had to configure two separate nodes, Group Assignment and Group Unassignment, to decide which groups to add and which to remove. Now a single task handles both.
The task evaluates your rules against the updated user. It then assigns or unassigns groups based on the Membership Action you choose: