Enforcing Password Re-Authentication in Tadabase Workflow Steps (Pharma Use Case)

App Development
1

Good day Tadabasers,

After watching Tim’s great video (linked below, around 04:55) where he re-uses the Profile Component, it got me thinking about whether the Login Component could also be repurposed to enforce authentication during critical Workflow steps.
(Video link: Build it with Tim - Hide Fields Based On User Preferences)

I work in the pharmaceutical sector, where certain workflow actions - especially those involving final approvals, reversals, or record closure - require the user to re-enter their password as an equivalent to a regulated electronic signature. Because of this, re-authentication at key points is not just a convenience; it is an essential control for GMP-aligned processes.

My initial idea was to embed the Login Component into a workflow form so the user would be prompted for their Current Password before the record progresses. However, when I tested this, the component automatically inserted all three fields: Current Password, New Password, and Confirm New Password. That behaviour does not meet the requirement, as I only need the Current Password — not a password-change flow.

Ideally, I am trying to achieve the following:

  • A single Current Password prompt as part of a workflow step.

  • Validation against the user’s actual Tadabase login credentials.

  • Enforcement of existing security policies, including account lockout on failed attempts.

  • A seamless re-authentication process before the workflow can move to the next step.

Has anyone managed to achieve this using on Tadabase?
Or is there another recommended approach for enforcing password re-authentication during workflow transitions?

Screenshots:
In the screenshot, when I click the Close button (action button), which will subsequently set Status to Closed, I want the user to be prompted with a password field upon password re-entering, where he will enter current credentials

image
image833×849 38.6 KB

Any guidance or ideas would be greatly appreciated.

2

Just an idea here, what about applying a PIN? Create a unique PIN for each employee in the User table (could be an employee ID, etc). Then, prompt for the pin when a change is made and the pin must match to proceed. You could create a connected table that logs all of the changes to the record along with PIN verifications.

I’ve used this PIN concept in a lot of different use cases (including easy front-end authentication where non-desk users can select their name and enter their pin to gain access to their areas of the system; actual auth handled on the back end)

3

Hi,

Thanks for the reply. Do you have any screenshots you can share on this, and how you get the PIN to be compared with what’s stored in the backend table?