The only thing I've been able to come up with is to create an a faux managed O365 account specifically for actions that require elevated privs. You can then set that one account to never expire. Aside from the benefit of a faux managed account, you also don't see items provisioned by the developer's account scattered all over the farm (or whichever account you use to elevate the action).
I have to agree, and another reason why Office 365 Nintex apps aren't really enterprise ready until a few critical features are implemented.
A thought I did have to make management simpler but risky is to store the user account password in a central place/list, with each workflow querying this list for the password and storing in a variable to use, when a password change is need it only needs to be updated in one place rather than 1000
So, since this has now become "a thing" in our organization, can anyone tell me how the passwords are stored within the Workflow Action assuming you just use the "value" and type it in manually? Is it stored plaintext there? I know you get the "bubbles" or "asterisks" but how is this password actually stored?
Can anyone give an update on the progress of this?
We have recently moved from SP and Nintex on Prem to online and finding the functionality between on prem and online very different.
Not being able to store secure passwords is not practical. The fact that this issue has been raised quite some time ago and nothing has been actioned is quite concerning.