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

Question

Question

Adding a Web service (Laserfiche Forms) when using directory server

asked on August 27, 2018 Show version history

Our client has Workflow and Forms on 2 separate machines on the same domain. I am trying to add the Web service for Forms in the Laserfiche Administration Console (External Objects, Web Services). (I've tried it in the designer with same result)

When I attempt this, I get this error: 

What exactly is trying to access what? I've tried changing credentials rather than "use default authentication" but am given the same results. Both workflow services along with the forms routing service are using the same domain service account. I saw some older posts about enabling anonymous authentication on the workflow websites so I've done that as well (even though I don't believe that is the answer). 

I've also tried changing the URL to the external URL that users go to - getting the same error. 

When users go to this URL they get 'redirected' to the Directory Server STS login, so I'm thinking this has something to do with it?

 

I've done this setup a few dozen times for customers but have never came across this error. 

The configuration on Forms Config is set for 'Workflow server' and the connection verifies. I've tried using SSL on it and without. 

Can someone enlighten me on what to look for? 

*There are no windows firewalls between the 2 servers. 

 

Thanks!

 

0 0

Replies

replied on August 27, 2018

Is there a specific reason you are trying to add Forms as a web service in Workflow? If the Workflow server is configured in Forms you shouldn't need to do that because you can use the built-in activities to interact with forms.

0 0
replied on August 27, 2018

Hi Jason, 

Yes I'm trying to invoke a BP in Workflow. I have to select the Forms server from the list, a list which is incorrect.

 

I had a BP and workflows internally on my system, and then exported and imported them into the clients Dev system. It brought the value of 'localhost' for the forms web service, which is incorrect as it's on a separate box. So trying to add a new one gives me the above issue. Hope this clarifies it for you. Thanks

0 0
replied on August 27, 2018

It's hard to say what might be happening there. When we set our environment up we configured the workflow server in Forms, then set Forms up with Default Authentication and everything works fine.

Is your production Forms configured to use this Workflow server? Also, is it using HTTPS or HTTP?

0 0
replied on August 27, 2018 Show version history

Hi Jason, 

They were setup but have not used anything yet in the production. I have just tried it and I actually get a different error....happy monday to me...

 

This item is now resolved - I had to apply this KB on the prod Workflow server: https://support.laserfiche.com/kb/1013919/configuration-information-for-tls-1-2

0 0
replied on August 27, 2018

Have you tried starting a Workflow from within Forms? That would at least help determine if it is a one-way problem or if they can't talk to each other at all.

0 0
replied on August 27, 2018

Yes Forms triggers workflow without issue (just tested again to ensure). It's just the other way that isn't working - Workflow to Forms. 

0 0
replied on August 27, 2018

Well I just tried something that I haven't yet....Rather than clicking the "Test URL" I just added it and tried to see if Workflow would see the BP's in Forms.....and it does. 

 

So it appears that it will work even though the URL test fails....

0 0
replied on August 27, 2018

I missed a screenshot, when I use the FQDN in the URL I get the following error:

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

Sign in to reply to this post.