Or if you omit the user in the connector configuation then you can set this on Flow user itself (or if you omit it here also user will be prompted for IFS credentials when they try to log onto Flow)
Thanks for the reply. Unfortunately, the option to use the Machine step level run as user isn’t really feasible for our setup (too many flows to update).
We need to look at the option to have user level login for the connector. We use AD to authenticate the Novacura users, I don’t think we can have the IFS passwords saved in Novacura. Also, if we don’t have the password, would the user be propted to login for every machine step to IFS? We have flows with multiple machine steps to IFS. We will need to investigate this option some more.
if you omit the password on the user you will be prompted for IFS password (for the IFS user you set on the Flow user) just once, when you log onto Flow client or Portal
I have been trying the above where the IFS10 connector doesn’t use a global user id. It works if I login to novacura by entering the Username and password manually. I get the prompt to login to IFS user, and the Workflows that use this connector will work without errros.
However, if I was to try and use the Sign in with your Microsoft domain account, then the user will be signed in, if I am logged into windows with the same account, but I do not get a prompt to login to the IFS user. It just signs the user in using SSO.