With the waive MFA permission being phased out, what are customers expected to do when they bring on a third-party consulting partner to create projects and those users need System Admin privileges?
#MFAThank you for that information. Our company does approve/allow one of the password managers. However, I do not use it and am unsure the corporate thought on a shared service user. I will ask my manager about that possibility.
"Are you saying that in a "Login As" session, the service user's managed package license does not work?"
I would say that it does not *fully* work. We are able to access the package content and do some things, but not the things that we ultimately need this Service User to do:
- We give our Service User a license to use this managed package.
- I have a license to use this managed package.
- When logged in directly as myself, I can schedule jobs "inside" this managed package.
- When logged in directly as the Service User, I can schedule this managed package's jobs.
- When I login as myself, then use the Salesforce "Login As" functionality to login as the Service User, I am unable to schedule this managed package's jobs.
I am unsure whether this is across all managed packages or just this one. But I can say that this is either a feature of this managed package or a known bug that they have embraced as a "feature."
Currently I am testing whether a Service User can schedule and run these jobs without "privileged" access. If so, we could split our current Service User into two and have one non-privileged with "standard" MFA for the managed package.
