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

Question

Question

Feature Request : Enable LDAP via Forms to accept multiple "base distinguished name" for

asked on March 27, 2014

 We currently have a customer with a unique LDAP setup that is looking to implement this feature.

They currently have users across multiple Organizational Units that needs to be added as participants.  Due to policies, users LDAP accounts need to have their password changed quarterly.  By using LDAP to add users, this would streamline the password updating process for individual accounts to access Forms.  This has been discussed with Laserfiche Support, and they have suggested that we post it as a request feature here.

3 0

Answer

APPROVED ANSWER
replied on April 18, 2014

Thank you for the feature request. I'll pass this along to the rest of the Forms team for consideration for a future release.

1 0
replied on April 18, 2014

Great to hear, Eric.  Thank you.

0 0
replied on May 21, 2014

Eric, is there any update to this?

0 0
replied on May 27, 2014

Eric, is there any update to this?

0 0
replied on May 6, 2015

We too use multiple OUs in our AD.  This would be very benificial for large WAN deployments like ours.

replied on May 6, 2015

Kip, this is supported as of Forms 9.2.1.

0 0

Replies

replied on May 29, 2014

We have a great need for this. We have principals underneath sub OU's of the main Users OU. In order to get access to all of the Principal users, we have to have the Base Distinguished Name point to the Users OU. The only problem is that there are over 3200 objects in it.

1 0
replied on May 30, 2014

I'm not the only one!

0 0
replied on June 18, 2014

Eric, is there any update on this feature request? Will it be implemented? If so, will it be in the near future? I have 60 Participant licenses to assign and it is next to impossible right now using LDAP because of how many users are being brought in (3200+).

1 0
replied on September 5, 2014

Thanks for the feature request!

 

It has been planned for next year's product update.

0 0
replied on September 5, 2014

Abby, is there anything in the works to help get around this problem before that update? It literally takes me 10-15 minutes to assign 1 Participant User license.

1 0
replied on September 8, 2014

Hi there,

 

You can batch import Participant users through Excel, .using script to auto generate .csv content. Will this help solve your problem?

0 0
replied on September 23, 2014

Hello

 We have this issue as well. We have to add around 2000 participant users and it took me over 10 minutes to add one user.

 I am open to the batch import mechanism but can we use that for LDAP (Active Directory) users as well?

- Philip

0 0
replied on October 7, 2014 Show version history

For us it would work if we could just specify our own LDAP Query. Our students all have different domains for their email addresses, so if we could exclude accounts that have an email address that matches that domain, it would make a world of difference. For example, if we had an LDAP Query or Filter field on the LDAP configuration popup where we could put in (mail=*domain), that would take our returned results from 10,875 to 1,405.

 

1 0
replied on February 20, 2015

This will be available as part of the upcoming Laserfiche 9.2.1 release.

1 0
replied on April 13, 2015

Laserfiche Forms 9.2.1 released in March, 2015 with multiple base distinguished names support for LDAP participants.

 

https://support.laserfiche.com/KB/1013596

 

0 0
replied on April 14, 2015

Thank you!

0 0
replied on April 16, 2014

This is a beneficial feature request since forms users could be widespread across multiple departments Enabling LDAP on the parent OU would work, but that could cause issues with Forms not being able to handle the entire list of entries if there are thousands of them.

0 0
replied on May 21, 2014

We just received another request for this feature.  When will this be available?  Thank you.

0 0
replied on May 27, 2014

Is there any update to this?

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

Sign in to reply to this post.