Import user photo from LDAP into S-N (reloaded)

[conmic]

Dear Community,
my company is now changing to Service-Now and I'm currently working on adapting it to our needs. I worked the entire day long on the import of the LDAP user photo into S-N and I really got to thank john.roberts who first published in 2009 the base-script for what I need, see this topic: Importing user picture from LDAP into S-N.

Unfortunately his script is out-of-date as calling packages directly is now prohibited with the Calgary release and also his script is not able to update existing photos in S-N. So I accepted the challenge and modified his script.
It's already working and I want to share it with you in a minute, but maybe you guys can help me on a few questions as I'm new to S-N and JavaScript (previously I was more working on MS.NET).

Let's start withe the requirements:

1. Only import JPEG pictures into your LDAP, else you need to modify the script (to be honest I don't know if LDAP supports other formats)

2. Make sure to add the value "thumbnailphoto" to the system property "glide.ldap.binary_attributes". This system property should already exist on the sys_properties.list, otherwise add it manually by following the instructions that can be found on the S-N wiki.

Note: john.roberts script was aiming for the "jpegphoto", you can also use such attribute but you need to change the previous mentioned system property and also the following script accordingly (simply replace each thumbnailphoto with jpegphoto).

3. Make sure to set the system property "com.glide.loader.verify_target_field_size" to true. By default it's false. Otherwise follow the instructions given on john.roberts script.

Now to the Script:

Go to your "LDAP user import" transform map and add a new onAfter transform script.

Sorry, I'm horrible in giving proper comments on scripts. Please refer to john.roberts base-script or simply ask me if you have a question.

//add user image from ldap thumbnailphoto attribute and keep records in SN up-to-date

//**first check and get the existing photo of the SN-record
//this is vital if we want to update the photo when it has been changed in LDAP
//however the more users there are and the bigger the stored pictures are, it might slowdown the import process
//It can be simplified but then SN-pictures will not be removed automatically when the picture has been removed in LDAP
var existingPhoto = new GlideRecord('sys_attachment');
existingPhoto.addQuery('table_name','ZZ_YYsys_user');
existingPhoto.addQuery('table_sys_id',target.sys_id);
existingPhoto.addQuery('file_name','photo');
existingPhoto.query();

//**check if there is a picture on LDAP
if (source.u_thumbnailphoto != '') {
    //**if there is no picture for the record in SN
    if (!existingPhoto.next()) {
        //**launch the function to attach the picture
        attachPhoto();
    }
    //**if there is a picture for the record in SN
    else {
        var sysEncodedAttachment = new GlideSysAttachment();
        var binData =  sysEncodedAttachment.getBytes(existingPhoto);
        var EncodedBytes = GlideStringUtil.base64Encode(binData);
        //**verify if the current existing SN-picture for the record does not match the current LDAP picture
        //if it does not match, delete the current SN-picture and launch the funtion to attach the new picture
        if (EncodedBytes != source.u_thumbnailphoto) {
            existingPhoto.deleteRecord();
            attachPhoto();
        }
    }
}
//**if there is no picture on LDAP
else {
    //**check if there is one on the SN-record and delete it
    if (existingPhoto.next()) {
        existingPhoto.deleteRecord();
    }
}

//function to attach a new photo from the LDAP to the SN-record
function attachPhoto(){
    var sysDecodedAttachment = new GlideSysAttachment();
    var DecodedBytes = GlideStringUtil.base64DecodeAsBytes(source.u_thumbnailphoto);
    var attID = sysDecodedAttachment.write(target, 'photo', 'image/jpeg', DecodedBytes);
    var newAttachment = new GlideRecord("sys_attachment");
    newAttachment.addQuery("sys_id", attID);
    newAttachment.query();
    if (newAttachment.next()) {
        newAttachment.table_name = "ZZ_YYsys_user";
        newAttachment.table_sys_id = target.sys_id;
        newAttachment.content_type = 'image/jpeg';
        newAttachment.update();
    }
}

So... as you can see in order to be able to delete the photo on S-N if it has been removed in LDAP, I need to load the entire S-N image-data for each user-record there is. Meaning the more users you have and the bigger the stored pictures are, the longer it will take to verify and import. If you guys have an idea how to optimise this, I'd be grateful! Otherwise we can simplify the script, but then the photo on S-N will not be removed if it has been removed in LDAP, however it will still be able to update changes.

As john.roberts also suggested, you can afterwards test the script only on a specific user by adding to the LDAP filter (sAMAccountName=DesiredUsername*)

P.S.: Unfortunately S-N has not yet the possibility to directly import the LDAP photo, this is the only possibility we have

[ppparmar]

No luck!! Tried few options and all failed.

[jason_mckee]

When you see [B@ strings (from GlideSysAttachment.getBytes(), for example), what you have is a Javascript wrapper to a Java byte[] object.

Assuming you've done something like:

var sysAttachment = new GlideSysAttachment();

var javaByteArray = sysAttachment.getBytes('some_table','some_sys_id');

To convert javaByteArray to a pure Javascript object, can do something like:

var javascriptBinaryData = GlideStringUtil.base64DecodeAsBytes(GlideStringUtil.base64Encode(javaByteArray));

Note that you could also loop through javaByteArray in a for loop and do the conversion yourself, but it's a little mind-bending since Java byte objects are signed values in the range -128 to 127 and Javascript represents binary data as strings of characters with charCode values of 0-255, so you have to brush off your twos-complement math skills.

All that said, make sure you actually need raw binary data and not base64 encoded data (in which case, stop with GlideStringUtil.base64Encode(javaByteArray)).

[Michael Kaufman]

I had another client with the same issue as you guys are having with the getting [B@ Strings in the import.   Here is how I fixed it.

1. Edit the system property called glide.ldap.binary_attributes. Set the value to objectsid, thumbnailphoto.

Or whatever your photo is called in ldap.

2. Rerun the import.

Also you want to follow all the other steps in Import User Photo from LDAP — ServiceNow ELITE.com

[jonas_waga]

I have gone through the steps once again, but still get the exact same results.

Tried with jpegPhoto and thumbnailPhoto (added them both to glide.ldap.binary_attributes) no luck... it seems impossible.

[erikbos]

Jonas, did you find a solution, did you check what is actually in the image field in your import table ?

Looks like I have exactly the same problem:

1) In our AD mugshots are stored in attribute thumbnailPhoto. When I query AD with LDAP using Apache Directory Studio it tells me type for this attribute is binary. When I save the attribute's contents with Apache Directory Studio as .jpg file I can view that file as image just fine.

2) I have added thumbnailPhoto to glide.ldap.binary_attributes on our SN instance (value of that property is "objectsid,objectguid,thumbnailphoto")

3) After an LDAP import the import table ldap_import's field thumbnailPhoto contains the text string "[B@ec74a44" for my test user. (you might have to personalise ldap_import's form or list to see this field obviously)

Shouldn't the value in this field be base64 encoded ?

When I change the code in the onAfter script from:

var DecodedBytes = GlideStringUtil.base64DecodeAsBytes(source.u_thumbnailphoto);

to    

var DecodedBytes = source.u_thumbnailphoto;

I get an attached file added to my test user that contains "[B@ec74a44", 10 bytes.So that confirms the code path itself works all the way.

So my hunch is that glide.ldap.binary_attributes is somehow not taken into account..

(This is on Eureka btw, access to LDAP is via mid server)