Answer
No — this was deliberately NOT implemented in Aurena, per R&D's own stated reasoning: adding a way for the two most powerful accounts (IFSAPP/IFSADMIN) to bypass SSO via a weaker authentication mechanism would effectively create a security backdoor into customer environments, which was judged too significant a security risk to introduce — even though R&D acknowledged the lack of an equivalent is genuinely cumbersome for support investigations. Two practical workarounds exist for critical investigation needs on non-production environments: (1) if Azure AD is the identity provider, invite the support user's account as an Azure AD B2B guest user and set up a corresponding Foundation1 user for it — this is the cleaner option since the guest account only needs to be invited, not granted extensive rights, just enough to log in; (2) temporarily reconfigure the environment's authentication settings — back up the current Identity Provider configuration from the IFS Middleware Server Admin Console, switch the Identity Provider to 'IFS Database' and save (this doesn't require a server restart on Apps10), log in with database authentication to get an authenticated session, then restore the original backed-up configuration and save again. The authenticated session obtained this way stays usable until it expires, but can't be renewed — if it expires, you'd need to repeat the temporary-reconfiguration steps to get a new one. Doing this on a test environment or a clone is strongly preferable to a live production environment given the (however brief) authentication-method change involved.