Problem configuring pas.plugins.ldap , "ERROR: Exception in Users; integer argument expected, got float"

1

Hi All,

Did anyone encountered this error while configuring the pas.pluhins.ldap ?

After filling in the required config and pressing "save", I get:

"ERROR: Exception in Users; integer argument expected, got float"

I checked on the ldap server log and the only thing the plone side did was to handshake, not query anything.

Thanks,

Oren

2

I'm experiencing the a similar issue with a fresh install of Plone and adding pas.plugins.ldap. My LDAP variables are the same as used on other Linux boxes which authenticate with AD without issue.

I don't see anything about an integer, however.

I just see "ERROR: Exception in Users" on the web interface and the following appears on the Plone server:

2017-03-29 13:45:35 ERROR pas.plugins.ldap Non-LDAP error while connection test!
Traceback (most recent call last):
File "/opt/plone/buildout-cache/eggs/pas.plugins.ldap-1.5.1-py2.7.egg/pas/plugins/ldap/properties.py", line 153, in connection_test
ugm.users.iterkeys().next()
StopIteration

3

@cfa you have two threads going here about LDAP... are they for different problems?

4

Yes - two different issues

Thread 1 = issue getting pas.plugin.ldap functional with Plone v5.0.7
Thread 2 = issue getting plone.app.ldap functional with Plone v5.0.7

Ultimately I was able to get the PAS plugin somewhat functional. The app.ldap plugin still cannot be configured using PLone v5.0.6.

5

please stop posting on plone.app.ldap and focus on pas.plugin.ldap only.

that's currently the only supported package to deal with LDAP integrations.

period.

6
7

Hi!
Please, how did you get the pas.plugins.ldap functional, I'm experiencing the same issue in Plone 5.0.8

2017-11-22T13:36:32 ERROR pas.plugins.ldap Non-LDAP error while connection test!
Traceback (most recent call last):
File "/opt/plone/buildout-cache/eggs/pas.plugins.ldap-1.5.2-py2.7.egg/pas/plugins/ldap/properties.py", line 153, in connection_test
ugm.users.iterkeys().next()
StopIteration

8

My guess is that your ldap server does not contain any users.

ugm.users.iterkeys().next()

A StopIteration exception is thrown by iterators when there a no items (left) to be consumed by a .next() call.
In this case it implies that users.iterkeys() has no users at all.

9

Thank you, for the guess!
Actually the problem was some configurations.
It should be like that:

Users search scope = SUBTREE
Users search query filter = (&(objectClass=user)(objectCategory=person))
Object class = top, container, organizationalPerson

Reserved key LDAP attr name
rdn sAMAccountName
id sAMAccountName
login sAMAccountName

Groups search scope = SUBTREE
Groups search query filter = (objectCategory=group)
Object class = group

Reserved key LDAP attr name
rdn sAMAccountName
id sAMAccountName