Import user photo from LDAP into S-N (reloaded)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2013 01:16 PM
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).
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2016 01:54 AM
Hi Brain,
We too have the same issue, picture was visible for long time, it suddenly stopped working.
We didnt modified anything. I can see te photo properly in user profile but it is not visible next to user name, it is displaying just initial.
We are on Geneva patch 8, we have done 2 patch upgrade after we initially implemented.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2017 07:06 AM
Please note that since Geneva, the Attachment creator needs a valid table name to work. You may want to change
'ZZ_YYsys_user' to 'sys_user' to avoid "Invalid table name" when the ECC_queue record is processed.
On the top search, search for both table_name = 'ZZ_YYsys_user' OR 'sys_user' so you can match the photo if it exist.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2018 12:37 PM
I have had this working for awhile in Istanbul and my Prod is still working. We are working on upgrading and we cloned down prod into dev, pictures where still working, upgraded to Jakarta and it stopped. I get the big X in the photo field. Kinda like when you don't have all of the bytes. u_thumbnailphoto is at 65,000 still so it did not truncate that. Not sure what is causing it to stop.
Anyone else on Jakarta and its working?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2019 04:37 PM
I think the photo attribute just needs to be set for the user record. Also added the filename extension after trying in Scripts - Background. Working in Madrid Patch 2:
//function to attach a new photo from the LDAP to the SN-record
function attachPhoto(){
var DecodedBytes = GlideStringUtil.base64DecodeAsBytes(source.u_thumbnailphoto);
var attID = new GlideSysAttachment().write(target, 'photo.jpeg', '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();
}
// Set photo for user
target.photo = attID;
target.update();
}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2023 04:04 PM
Has anyone got this to work in Tokyo? I have not been able to get it successfully working. I believe there is an issue decoding the thumbnail and this part of the script never runs:
if (newAttachment.next()) {
newAttachment.table_name = "ZZ_YYsys_user";
newAttachment.table_sys_id = target.sys_id;
newAttachment.content_type = 'image/jpeg';
newAttachment.update();
}