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

Question

Question

What causes Forms to use SID instead of sAMAccountName for Usernames with Active Directory

asked on June 23, 2021

We had an instance where everyone's username was their SID for awhile, a long string of characters, instead of using the sAMAccountName. By default it has always used the sAMAccountName without any special configuration.

Where is this configured and what would cause it to use the SID instead?

The system that had the problem is setup use the standard Kerberos connection, not LDAP (I know there is a specification of which metadata to use for username in the LDAP server configuration).

0 0

Answer

SELECTED ANSWER
replied on June 23, 2021

Generally speaking, when Laserfiche applications (across the board) cannot query AD for user attributes for whatever reasons, they will display the user SID instead. I've seen SIDs show up in place of usernames in LFS and LFDS too. Couldn't speak as to why that happened to the particular Forms instance in question.

0 0
replied on June 24, 2021

Oh so it just means the AD controller was down during the last sync. The problem with this is that when forms tries to assign a task using the original username, it says the user does not exist, because their username changed.

It would be better to just leave the user names as they are if the sync can not run.

0 0
replied on June 24, 2021

If all the usernames flipped to SIDs then yeah, that's most likely. 

If you ever see one or a few flipped to SIDs while others from the same AD are fine, that usually means those users were deleted in AD but not removed from Laserfiche (so the attribute query fails only for them).

0 0
replied on June 24, 2021

Ok, all were switched to SIDs until the next sync which causes the error "No User Is Assigned to the Task" in Forms.

0 0
replied on June 24, 2021

Is this Forms with LFDS or Forms with repository authentication?

0 0
replied on June 24, 2021

LFDS Auth

0 0

Replies

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

Sign in to reply to this post.