We’re using a custom HTTP module for http authentication. However, we’re interested in using URL integration. In Appendix B in your WorkflowGen Administrators Guide (page 173), we found:
“To enforce the appropriate security in WorkflowGen, these URL launches require users to authenticate themselves and therefore work best with Integrated Authentication.”
How has this been done? Do you have any suggestions on how to do this?
The reason I’m asking about this is because we’re interested in using the Remote Launch service - which uses URL integration to launch the initial request. In order to use this, we’d need to somehow get around the security that IIS is applying to the URL and then launch the request using some other username.
The process remote launch will work fine with custom HTTP authentication. It’s like Basic IIS authentication which means when you call the URL to start a new request in WorkflowGen, you will need to provide a service account username and password (which is an active user in WorkflowGen and this user is also part of the Requester participant of the process that you want to launch).
This service account will be the requester of the new request, unless you want to impersonate another WorkflowGen user (e.g. Launching a new request on behalf of another user) by specify the username in the parameter REQUESTER_USERNAME of the process remote launch URL.
For more info, see: