Secure Password variable including Workflow Constants
When designing a workflow for O365 a lot of Nintex Store actions like 'Create Site' require an account and password explicitly. As I am -designing- the workflow I do not want to know the actual Workflow Account password executing these actions, that's for the admins to know. The only way to enter these passwords is by using plain text either directly or by means of a Text variable. So I would propose a new 'Secure String' or 'Password' variable so at least I can call someone to type in the password without me knowing it. Of course it would be best that these actions don't require an extra direct password or just send a mail to the user indicated asking him to login and trust the execution of the workflow.
Interesting to have this option to store credentials for example.
More then a year iunder review for something so relevant. As John said, may sites having many workflows with many actions makes it unmaintainable. Reading it from a list is a security breach and a hidden list is not possible either.
Can you please come with a solution, an update or anything?
Stefanie Sloper commented
Any updates on when this will be available? It's very labour intensive to have to update credentials manually in multiple actions, across multiple workflows and multiple site collections
I don't like having to hard code Username and Password within a web request or use a variable from where I have retrieved creds from another list.
It would be good if it was possible to obtain credentials from the secure store which is designed to keep things secure.
John Luangco commented
I agree with this as being very important for using workflows in office 365 tenant. Many workflows we work on have to go through dev, test, uat and production. Many of the actions still require the input of passwords. Although we use settings list to store other details like username, tenant url, putting the password into a list is not viable for many organisations. Thanks and looking forward to this feature being released in the near future.
Jeroen Struik commented
I agree. Even better would be a global secure password / user account variable.
And how to use Secure String in Nintex wf 2013? I just can use it in connection string field.
Sjoerd V commented
see also: http://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/4655885-parity-in-the-query-list-action for some more suggestions