Question

The server has rejected the client credentials.

Workflow

Updated January 17, 2024

asked on January 6, 2024

Hi,

We are trying to attach in monitored repository which is already registered in another workflow server. But getting the following error. What could be the problem here?

We are simply trying to input main Workflow Server's IP address and when we lose focus, the above error appears.

0 0

Replies

replied on January 8, 2024

Is this server on the same domain as the one you're trying to attach to?

0 0

replied on January 8, 2024

All servers on the same WORKGROUP and all server can ping/communicate with each other. We have two environment of multiple servers each on private cloud with Laserfiche RIO 11.

Production Environment:

LF PROD Directory Server
LF PROD Server
LF PROD Workflow
LF PROD Webclient
LF PROD Forms
LF PROD DB

Stage Environment:

LF Dev Server
LF Dev Workflow
LF Dev Webclient
LF Dev Forms
LF Dev DB

I have installed additional LF Workflow Server on LF Dev Server and trying to attach monitored repository from LF PROD Server which is already registered in LF PROD Workflow. However, I'm able to register in monitor repository in LF Dev Server if remove the repository from LF PROD Workflow (but no able to attach).

0 0

replied on January 8, 2024

Workflow uses Windows authentication for its security, so a domain is required.

1 0

replied on January 8, 2024

But the question is, why I'm able to register in monitored repository and not attach? Our current repositories are already registered in workflow monitored repositories.

Repository from LF PROD Server is registered in LF PROD Workflow.

Repository from LF DEV Server is registered in LF DEV Workflow.

If domain is the requirement for windows authentication then it should not register as per my understanding.

0 0

replied on January 17, 2024

When you register a repository to a Workflow Server, Workflow only needs to connect to the repository using the username and password you provided for that repository. You are likely running the configuration utility on the Workflow Server, so you have already authenticated to that machine and Workflow verified your rights to run the utility locally.

When you attach a repository, it's so 2 or more Workflow servers can share the password to connect to a single repository. So the configuration utility on Workflow Server 1 needs to be able to connect to Workflow Server 2 to verify that the currently logged in Windows user is an administrator on Workflow Server 2 and has the rights to complete this configuration. This is where Windows authentication comes into play.

0 0

You are not allowed to follow up in this post.

Question

Question

The server has rejected the client credentials.

Replies

Sign in to reply to this post.