Hi!

First of all I must say that this module is life saving and IMHO it is crucial in helping Drupal moving toward enterprise users. One huge thanks for all who are working on this cool module. And now the problem. :)

I suppose it is nothing big, but when I go to user page (e.g. www.example.com/user/9) I got this message:

Beside this little warning everything is (almost) working like a charm.
I don't know what (extra) information could help in troubleshooting this issue, so any kind of feedback will be appreciated.

Tnx again, cheers.

Comments

miglius’s picture

miglius commented

Try navigating to 'admin/settings/ldapdata', then choose your ldap server and just save the settings. Does this solve the issue?

roberto.ch’s picture

roberto.ch commented

me to...

but save the ldap server in 'admin/settings/ldapdata' solve the issue.

izkreny’s picture

izkreny commented

Tnx Miglius for quick reply.

It is not quite correct that just saving/updating settings in 'admin/settings/ldapdata' makes warning message go away, at least in my case.

Details: I have situation where I just want to allocate Common Name value from active directory to profile_full_name field, and I can only read from LDAP server (so I choose Same, but read-only mode. in 'Should Drupal account fields be mapped to LDAP Attributes?').

Also I would like to make all LDAP attributes' values not readable/editable by User, so according to that fact I left all checkboxes in "Attribute visibility & access control" section unchecked.

With settings like I mentioned above you got the warning message, but when I just check 'Readable by User?' Email attribute, then warning message disappear.

It looks like that workaround for not showing the warning message is making at least one LDAP attribute value readable by user.

Hope this info will help in solving issue.

miglius’s picture

miglius commented
Assigned: Unassigned » miglius
Status: Active » Fixed

I have committed the fix to the cvs.

izkreny’s picture

izkreny commented

I applied patch and there is no warning message and everything is working like it should. :)

Tnx again.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

sunescan’s picture

sunescan commented

Hello,

I'm having the same warning, what must I do to apply the patch?

Thanks!!!!

izkreny’s picture

izkreny commented

@sunescan: try with the latest dev version: http://ftp.drupal.org/files/projects/ldap_integration-6.x-1.x-dev.tar.gz (2008-Aug-22).

sunescan’s picture

sunescan commented

Hello,

I need a version ready for a production use, I think the dev version isn't it.

Any idea?

Thanks a lot!

jerome72’s picture

jerome72 commented
Assigned: miglius » Unassigned

Hello,

I had the same problem and solved it in admin/settings/ldapdata/edit/1
I checked the options Readable by User? in the section "Attribute visibility & access control", and the the error messages disappeared.
Hope this can help
Regards

izkreny’s picture

izkreny commented

@sunescan: I agree with you, it would be great (and recommended) to use stable versions of modules for production sites. But, I can testify that with LDAP integration version 6.x-1.x-dev (2008-Aug-14) I don't have any problems, everything works just fine although I'm using dev version of module which is almost two months old.

@jerome72: Version of LDAP integration module that I'm using doesn't have that issue (and as you can read it should be solved). So, just to repeat: I have chosen "Same, but read-only mode." in "Should Drupal account fields be mapped to LDAP Attributes?:" section, and I don't have checked any Readable by User? option in the section "Attribute visibility & access control". The result is that I don't have any error messages, and with same options you have...hm...this is really strange! :)

keenlio’s picture

keenlio commented

I do like this then the error message gone provided you all don't want to map:
Go to LDAP DATA -> Edit -> Advance Configuration -> DN for reading/editing attributes:
then put in the attributes and passwords which you use to setup the LDAP Server under Login Procedure->Base DNs. Passwords I use password supplied to the field 'DN for non-anonymous search:'.

Hope this help you all.