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

Discussion

Discussion

LDAP Server Profile name appended to Username

posted on October 17, 2019

I have many servers setup with an LDAP connection, but this one is acting a bit strange. Normally the domain name is appended to the username but in this case whatever we name the LDAP server profile name get's appended to the username and they must login with this.

For example the LDAP Server Profile name right now was named "Primary". So all the usernames are username@Primary and they must login this way. Does anyone know how to turn this off?

0 0
replied on October 17, 2019

username@profilename is the expected behavior for LDAP profiles, as described in the help files.

Since you are able to chose the LDAP profile name, I recommend changing the profile name to the whatever name (such as the domain) would be more intuitive for the users to type in.

If this system is using LFDS, note that the LDAP profile name in the Server configuration should match the Identity Provider name in LFDS (which is also customizable).

1 0
replied on October 17, 2019

Ah I see, never noticed this before. It does let me update it. Can I remove it altogether? I really don't need an @ appended to the username.

0 0
replied on October 17, 2019

The Laserfiche Server relies on this value to know (1) that it must use LDAP and (2) which LDAP profile should be used.

It's possible that in simple scenarios with only one LDAP profile and no repository or LFDS Laserfiche users, the experience could be improved to have a default of "use LDAP, and use this profile", but there is no such setting at this time.

1 0
replied on October 18, 2019 Show version history

Oh, there is a reason to have more than one ldap connection? The Repository and Forms both hook up to the ldap service separately, but you can only have 1 connection when it comes to Forms, so it must be a repository specific feature to have 2. I noticed Forms allows multiple base dis names, but the repo only allows 1.

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

Sign in to reply to this post.