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

Question

Question

Common Profile Authentication - Windows Account

Workflow
Updated September 24, 2015
asked on July 9, 2015

Is it possible to use a Windows Account loaded to a repository through Active Directory as a common profile connection in Laserfiche Workflow?

I seem to be having no luck with the domain/username in the authentication while trying to create the profile.

0 0

Replies

replied on July 9, 2015

No. The connection profile is used by the Workflow Server when running workflows, so the Windows account would be the server account. That was going to introduce some confusion over which Windows account is used at design time, so we decided not to support it.

What functionality would it give you over a Laserfiche account?

1 0
replied on September 23, 2015

Having that functionality would allow those with multiple repositories use only one license for Workflow as opposed to taking up an extra license for each repository.

0 0
View 1 previous reply
replied on September 23, 2015

The connection profile user does not need a named user license.

0 0
replied on September 24, 2015

I am not sure I follow. When creating a Workflow or a Quick Fields Session, a Laserfiche permissioned account must be used in order to access the repository, the metadata and create documents. Are you saying this account does not need a license?

 

0 0
replied on September 24, 2015
0 0
replied on September 24, 2015 • Show version history

That's right. Workflow does not need a named user license because it's an automated service. It needs the appropriate rights and privileges, but not a license.

Quick Fields does need a named user license because there's an user driving the scan process. When Quick Fields sessions are used through Quick Fields Agent, they do not use the named user license either. So for example, a session set to Windows Authentication will use your named user license when you open it in Quick Fields. But when Quick Fields Agent runs it, it will use the service's login and that user doesn't need to be assigned a license.

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...