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

Question

Question

Find User activity is searching for windows accounts by Domain\username and cannot find them with that string in Active Directory.

Workflow
Updated April 7, 2015
asked on August 22, 2014

I've gotten switched over to Rio licensing so my users are all Windows accounts and all the full names and emails are stored in Active Directory already so I want to use that as my Trustee Directory.

 

When workflow sees the username it sees DOMAIN\Username so the %(Initiator) token for instance will read DOMAIN\Username. I'm trying to retrieve the full user info into tokens with Find User activity and point to %(Initiator) for the Account Name.  The problem is it can't find it because it terminates and says DOMAIN\Username is not found. When I use the Configure Trustee Directory dialog to search for the user I can ONLY find it if I search for Username only. Searching for DOMAIN\Username cannot find any of my users.

 

How do I retrieve my users in Workflow activities when they're identified to Workflow as DOMAIN\Username?

 

(without resorting to something really stupid like pattern matching the DOMAIN out of the string for every time I want to refer to an LDAP user)

0 0

Answer

SELECTED ANSWER
replied on August 25, 2014

I can confirm that I can make this work with a DOMAIN\\(.+) pattern match and it does find the user. It just seems clumsy that I should have to do that. Definitely takes away from the idea that end users can do workflow design.

1 0

Replies

replied on August 24, 2014

Pattern matching it out is the only way I've gotten this to work. In some AD scenarios that I've seen, you do need the Domain Name for the lookup. So, either way I think this token only satisfies half of the possible scenarios out there.

1 0
SELECTED ANSWER
replied on August 25, 2014

I can confirm that I can make this work with a DOMAIN\\(.+) pattern match and it does find the user. It just seems clumsy that I should have to do that. Definitely takes away from the idea that end users can do workflow design.

1 0
replied on August 28, 2014

Yup, thanks for this.

 

I've been banging my head against this for a few days now.  Find User doesn't find if we have DOMAIN\user but the pattern matched "user" works fine.  Your tip got me working.

 

I'm wondering if the BP notifications won't work either.  I suspect I will need to add email addresses for the BP participants even though they are AD users.

0 0
replied on August 25, 2014

What version of Workflow is this? Searching for domain users by account name using the DOMAIN\username should work. We did hotfix an issue recently where the search was mistakenly retrieving groups in some cases.

0 0
replied on August 25, 2014

We are using 9.1.1.381

0 0
replied on September 29, 2014

Hi Jeremy,

I'm curious to know if you ever found a solution to your problem? We also switched our Rio users from LF Named accounts to Windows Accounts on WF ver 9.1.1.365. For us the Find User activity works fine for most users. We switched 240 users and only 8 have a problem that Workflow does not find them using the Find User Activity.

0 0
replied on September 29, 2014

Vincent, this is not the same issue. You are using a Laserfiche trustee provider in Workflow, so even though you are using AD users, you are querying their name from the Laserfiche server.

0 0
replied on April 7, 2015

Did anyone ever find a solution to this?

 

It seems Laserfiche sees my Windows Accounts as DOMAINNAME\USERNAME and a "Find user" action from the AD directory doesn't work.  I have to put in a pattern matching step to strip off the domain.

0 0
replied on April 7, 2015

UPDATE: this only happens when you start out with a Laserfiche group and search for its domain users. Then take those users and look them up in active directory by account name. The Laserfiche server returns active directory users in the DomainName\AccountName format, Active Directory's account name property does not include the domain name prefix.

Given that it's only an issue when different types of trustee directories are involved, the pattern matching approach is the right one for getting the name in the expected format.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...