Notice: Undefined index: ldap_authorizations in _ldap_authorizations_user_authorizations() (line 294... ldap_authorization.inc).

Please test and file bugs against 7.x-2.x-dev.

Hi

I know it's a while ago but did you end up using this workaround and could you provide a patch to the current codebase?

I get the same error as comment #1 immediately after logging in using LDAP authentication.

Notice: Object of class stdClass could not be converted to int in drupal_write_record() (line 7340 of /srv/www/htdocs/drupal/includes/common.inc).

The LDAP successfully authenticates and creates a user record pulling correct role association etc. I have placed a random echo:

7339      if ($info['type'] == 'int' || $info['type'] == 'serial') {
7340 echo $field.": ".$fields[$field]."(".gettype($fields[$field]).")<br>";
7341        $fields[$field] = (int) $fields[$field];
7342      }

just at the line in the error.

I got the following:

fid: (NULL)
uid: 0(integer)
filesize: 17095(integer)
status: 1(integer)
timestamp: 1488301075(integer)
uid: 200(string)
created: 1488301075(integer)
status: 1(integer)
fid: (NULL)
uid: 0(integer)
filesize: 17095(integer)
status: 1(integer)
timestamp: 1488301075(integer)
uid: 201(string)
created: 1488301075(integer)
status: 1(integer)

Since I am echoing presumably before the completion of the bootstrapping, the page does not complete and ends at above.

We can see that there are string and NULL in this integer conversion. In respect with NULL, since 0, null and false can be the same in their loose comparison (http://php.net/manual/en/types.comparisons.php), I sort of suspect that uid conversion from string is more suspicious.

Now as I said, as for me, it creates a user record ok from LDAP authentication and pulls the right info although it returns an error. The error is only a Notice after all, it is not really an serious error per se although it is annoying.

The immediate solution is either to suppress the error display level (as per http://php.net/manual/en/function.error-reporting.php) somewhere appropriate or to suppress producing the error using @ in line 7340 just before "@(int)".

Now this is LDAP module issue support, so I am not sure if you can do anything about values you pass to drupal_write_record() function which is where this error message is produced. I mean, even my above echo ends up being nothing to do with this NOTICE error, it probably helps to check the values as it is to do with a data type conversion issue. I have not been able to dpm or var_dump successfully as I trying to debug in hurry as it seems to create a "serious" code integrity issue so that it only returns HTTP 500 internal server error. (I could be spending more time I suppose...)

Just for your info, I have D7.54, Postgres 9.4.6, PHP 7.0.5 and on OpenSuse:

me@myserver:~> lsb_release -a
LSB Version: n/a
Distributor ID: SUSE LINUX
Description: openSUSE Leap 42.1 (x86_64)
Release: 42.1
Codename: n/a

For now this will suffice:

$fields[$field] = @(int) $fields[$field];

Although I should not go on like this for a long time in the core codes.

Hum, seeing issue contributions to do with drupal_write_record and LDAP module, I came to this, which rings a bell:

https://www.drupal.org/node/2123773

as I also have thumbnailPhoto mapped against Drupal's "Property: Picture" attribute and indeed I see no photo showing up from LDAP. I may give it a go...

Bingo, my issue resolved and I have got no notice message either. @thisisjoe, can this be a solution to your issue???

Just a head's up, the change in the OP now works to suppress the error against 7x.-2.2.

Ah, fun. Turns out how userPictureFromLdapEntry() handles images is entirely broken.

Thanks for the input.

I believe that the changes I've made to the picture import should have fixed this.

Please reopen of you still can reproduce this with current dev.