Skip to main content
Open

Re-authentication for Critical Administrative Actions in FME Flow

Related products:FME Flow
  • February 25, 2026
  • 5 replies
  • 119 views

tino
Supporter
Forum|alt.badge.img+28

I would like to propose an enhancement to FME Flow regarding administrative security.

Although administrators are already authenticated when logged into the system, certain critical actions pose a significantly higher risk and impact. These include, for example:

  • Creating or restoring backups

  • Connecting or modifying Authentication Services

  • Adding or deleting users

  • Changing security-related configurations

  • Other high-impact administrative operations

To increase security and reduce the risk of unintended or malicious changes (e.g., in case of session hijacking, unattended sessions, or compromised credentials), I propose that FME Flow require administrators to re-enter their password before executing such critical actions.

This additional verification step would:

  • Strengthen security for sensitive operations

  • Reduce the risk of accidental misconfiguration

  • Align with best practices for secure administrative interfaces

  • Provide an extra layer of protection without significantly impacting usability

The re-authentication prompt should only appear for clearly defined high-risk actions to maintain a smooth user experience for routine administrative tasks.

5 replies

rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • February 27, 2026
New→Open

nathanatsafe
Safer
Forum|alt.badge.img+9

Hi FME-ers,

For anyone following this idea, apologies for the notification noise. This idea recently went through a couple of status changes stemming from an internal tidy-up on our side, not from a decision about the request. The erroneous changes have been reverted and this idea remains open.

To be straight about where it actually stands:

There is re-authentication work planned for one specific administrative action — changing the security tier in FME Flow — currently targeted for a release later this year. That's a narrower slice than what this idea covers.

The broader request, requiring re-authentication before critical administrative actions generally, is tracked on our side but is not currently scheduled.

cc. ​@tino 


redgeographics
VIP
Forum|alt.badge.img+63

May I suggest that “removing a repository” is one of those critical tasks too, as I found out today 😅

(the damage is limited, there were only 2 workspaces in that repository and we hadn’t actually set up automations yet, so all I had to do was recreate the repository and publish the two workspaces again, but it was definitely an “uh-oh” moment)


cfvonner
Supporter
Forum|alt.badge.img+32
  • Supporter
  • August 24, 2026

Whatever solution to re-authentication is implemented, it needs to accommodate the various ways an administrator can sign in (including Windows/Azure Active Directory, Generic Directory, and SAML).


tino
Supporter
Forum|alt.badge.img+28
  • Author
  • Supporter
  • August 25, 2026

May I suggest that “removing a repository” is one of those critical tasks too, as I found out today 😅

(the damage is limited, there were only 2 workspaces in that repository and we hadn’t actually set up automations yet, so all I had to do was recreate the repository and publish the two workspaces again, but it was definitely an “uh-oh” moment)

Oh, i’ve to hijack my own idea thread for another thing:
It would be very nice if the dialog to remove any element would at least show the name of the element in the confirmation dialog.
Currently you have to mark the checkbox and then scroll up again to the action/remove button and then you get asked if you really want to remove “an element” with no hint in any way, what you’ve selected. On production system i always cancel and re-check the selected item twice to not delete the wrong one...