Hi ‌

In workflows you can only use credentials to call a web service that are stored as a Workflow Constant. These can be any credentials but it is better to set up a service account that has permissions and whose password will not change or risk using credentials of a user whose password will change or who may leave the business

Hope this helps

Agree with this. Instead of making the web service available to everyone with permission it's easier and more secure to have a specific service account set as workflow constant and call the web service with these credentials.

If you need the current users logon name however, you can easily pass the current user's name or logon name to the web service by picking it from the workflow context.

Best regards

Enrico

Not sure that it would be more secure since most users have access to this web service. We are using a service account now. We have seen some curious issues with this.

What issues do you see with this configuration?

Sorry for the delay, the urgency for this was overtaken by a migration.

The issue was that even though all our groups (we are referencing users.asmx) are readable by all users, the account would not always return data from all groups (we were looking at three, to get the users to specifically address tasks). Adding the account to a group that owned the group of interest would resolve the problem, but should not have been necessary, and was not necessarily desirable.