in ldap.c before rad_assert(handle == conn->handle);
i've put this debug line
DEBUG("rlm_ldap (%s): Rebinding to URL %s", conn->inst->xlat_name, url);

and the result is

(0) Performing search in 'dc=intra,dc=ismaa,dc=it' with filter '(&(objectCategory=person)(objectClass=user)(sAMAccountName=garofalod))'
(0) Waiting for search result...
rlm_ldap ((null)): Rebinding to URL ldap://ForestDnsZones.intra.ismaa.it/DC=ForestDnsZones,DC=intra,DC=ismaa,DC=it
ASSERT FAILED src/modules/rlm_ldap/ldap.c[1030]: handle == conn->handle
Annullato


2013/10/28 Davide Garofalo <davide.garofalo@gmail.com>
OK FR3 development team,
I understand... urra!!!!

I downloaded the latest release of FR3 directly from the git. But now I get this error:

(0) Performing search in 'dc=intra,dc=ismaa,dc=it' with filter '(&(objectCategory=person)(objectClass=user)(sAMAccountName=critest))'
(0) Waiting for search result...

ASSERT FAILED src/modules/rlm_ldap/ldap.c[1028]: handle == conn->handle



2013/10/26 Davide Garofalo <davide.garofalo@gmail.com>
ok, i tried whit a new istance of ldap -> ldap test {....} and in default site in post-auth section i call -> if (test-Ldap-Group == "foo"){......}  but i've the same error....

I am available for further testing.

Davide


2013/10/26 Arran Cudbard-Bell <a.cudbardb@freeradius.org>

On 25 Oct 2013, at 21:04, Davide Garofalo <davide.garofalo@gmail.com> wrote:

> ok, I tried to follow your advice but I do not think I've followed the right path
> I created a new virtual_server named 'test' for client localhost in clients.conf file.
> In sites-enebled directory, i created a new file named test that include server test { ... .... }, but the results is the same error.

*sigh*

No, it’s referring to instances of the module… Why would a different virtual server require a different LDAP Group attribute?

ldap <instance> {

}

will result in

<instance>-LDAP-Group being registered

Which you should then use as

<instance>-LDAP-Group == "foo"

-Arran


> Approximately, you know when you distribute a new version of freeradius?
> one week or some months? ;)

Faster when people test the code so we can be sure it works. Should be a week or two. But honestly with v3.0.x there are no major code changes, -v includes the git commit hash, there's no reason to not run that in production.


Arran Cudbard-Bell <a.cudbardb@freeradius.org>

FreeRADIUS Development Team

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



--
Davide Garofalo





--
Davide Garofalo





--
Davide Garofalo