You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Forms Workflow Connection Test is improperly reporting success

Forms
Updated July 20, 2022
posted on November 1, 2020

During a new forms installation we were configuring the workflow connection. We found that it gave a success message even when the connection was unsuccessful.

After much digging we found a special requirement of Forms Workflow connections which was unknown and unusual.

The source address (the address workflow uses to identify itself when making network communications) must match the address resolved by the DNS entry entered into the Forms Configuration for the Workflow Server Name.

In this case the server had 3 IP addresses and the DNS resolved to one address while the server likes to use another address as it's source.

This was confusing enough to find itself but the biggest problem was that we were getting a success message and did not even know that the workflow connection was not configured, while workflow kept trying to tell us that it was not configured and we would confirm over and over again that it was testing successfully.

If it would have said error: The source IP address must match the resolved IP address we would have had a lead to go on at least.

1 0
replied on November 1, 2020 • Show version history

The "Workflow Connection Test" you refer to is the "Test Connection" button on Forms Laserfiche Tab? It will give successful message if Forms can connect to the Workflow server configured by calling the API provided by Workflow ({workflowserver}Workflow/api/workflow), it is one-way check, and will not check whether Workflow server can connect to Forms calling the API provided by Forms({FormsServer}/forms/api/BusinessProcess/Listing). To check whether Workflow server can connect to Forms need to click the "Test URL" button from Workflow side.

What Forms can improve is adjust the error message "Service unavailable because the Workflow Server is not configured in Laserfiche Forms. Please configure the Workflow Server in the Laserfiche section of the Forms Configuration page. [LFF5206-WFAPIAccessDenied]" logged to include the situation that the request source IP address must match IP address obtained based on the configured Workflow server name.

1 0
replied on November 2, 2020 • Show version history

Ok yes, that is how we learned that "Workflow Server in the Laserfiche section of the Forms Configuration page" was not configured. The problem is when we are told this by workflow, we go to the Laserfiche section of the configuration page and it says "Everything is great!"

This lead to the finding of a needle in the haystack of answers where we could have had a bit more direction.

We can't know of any unique custom blockers to connections that might be buried in some official document somewhere, it helps to have that information pop up when that block is reached in the config utilities, or even an error code that leads to a KB article would be good as well.

 

0 0
replied on November 2, 2020

This error is not a very common one so there is no dedicated KB for it. We will update the error message to something like  "Service unavailable because the Workflow Server is not configured in Laserfiche Forms or the IP address resolved by Laserfiche Forms based on the configured Workflow Server doesn't match the IP address from the request sent by the Workflow Server."

1 0
replied on July 20, 2022

What was the fox for this scenario? I am running into the exact same issue. Everything works except the calls from Forms to WF. I believe this is because Forms is sending a different IP than WF expects in its calls.

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...