2-Step Auth dilemma

[Jim_OFlaherty]

As we all know, Adesk has moved /is moving to a 2-step authorization process to log into your applications.

That's fine and dandy for the general user, but how do us Admins/Managers deal with this when we need to do installs/updates that require configuration/set-up as the user, especially if the user isn't available or has the code going to their phone? (I can access their email if need be)

I have to assume there's a way around this that I'm not thinking of.

[brian.strandberg]

What I have been doing is signing log on to the users computer as them, when I need to log into Autodesk I use my credentials, do what I need to do, then log back out of my Autodesk Credentials.  So when the user gets the computer it is setup, and they just need to log on when they launch an application.

[Jim_OFlaherty]

Understood, but that's not the case here.

We use SSO and thus, as far as I am aware, to configure settings in Inventor for example, I have to do such as the user.

Thus needing to log into their Adesk account in the application (Inventor, Acad, Vault, etc) so those settings are set to their login/profile.

If I do such under my log-in, only I will see the settings, the user will still be at default.

Or has something changed that I'm just not aware of and need to update my own practices?

[brian.strandberg]

Got that.  We are not on SSO yet.  When I log on to the Autodesk Account through the application, the settings will still apply to the current windows profile.  Not sure how this will apply in an SSO context :(.  That is on the longer-term IT todo list.

[Anonymous · Accepted solution]

Well, not a fix, more of a workaround for now, but it seems we are allowed to disable this feature:

Disable 2-Step Verification (autodesk.com)

If I recall correctly, this process was to be adopted by all users, I think there was even a "drop dead" date for such.

Sure would have been nice to get a notice of such for those who activated this when it was originally requested.

***note: apologies for any confusion. I was unknowingly still logged into my work acct when I posted the issue. Once I found/figured out the solution, I posted such under my normal acct. No funny business at play here folks.***