Need a way to use an unauthenticated workfront service account for Fusion connection

[#1]

Description -  In the past, as an admin we could use a "login as" to authenticate to an account and use that to establish a fusion connection.  With the new Unified Experience this no longer works.   We need a way to establish this connection, whether it is through setting up an OAUTH2 Application in Workfront and using that in Fusion or other way.  

Why is this feature important to you -Tying fusion to a live user is risky since a user may be deactivated.  It also provides a poor user experience when the updates say Josephine Admin did this, rather than "Workfront Automation" did this.

How would you like the feature to work -  

Current Behaviour - Broken.  Can no longer set up a Fusion Connection to a service account.

[#2]

Thank you for raising this. Without that ability, I will continue to not be able to migrate my org to the admin console as that would put us out of compliance with our IT Security policies and best practices. Tools that act on their own within platforms must have a clearly defined audit trail of their actions that can be distinguished from the actions of normal person-accounts. 

[#3]

With the admin console, we lose the ability to login as another user? 

[#4]

No, you can still login as, but the fusion connection piece is tricky.  We used to be able to use that for establishing the fusion connection and that seems to have gone away, as you are required to login using the standard authentication (username/password) when setting up the connection, and the user gets authenticated through the console method (either adobe or your SSO).