
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2016 09:48 PM
I noticed that if you export these from AD they come out as Hex and when imported into SNOW they seem to be BASE64.
Example:
On a file provided from AD administrator, the guid is as follows: 9e5bab01-07dc-4ba1-a88f-93342f4b0927
Yet that same group when imported into SNOW shows as: AatbntwHoUuoj5M0L0sJJw==
I have found 1 website that accurately converts these from one to the other.
Online GUID Conversion Tool To Convert Hex Base64 Int
Is there a way to convert 9e5bab01-07dc-4ba1-a88f-93342f4b0927 to AatbntwHoUuoj5M0L0sJJw==
Better yet, is there a way to force SNOW to import it in HEX to begin with instead of forcing it to BASE64?
https://youtube.com/watch?v=zYi8KhP9SUk
Solved! Go to Solution.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2017 04:32 AM
I found the following will prevent the field from being modified from the original guid in ldap.
http://wiki.servicenow.com/index.php?title=Available_System_Properties#gsc.tab=0
http://wiki.servicenow.com/index.php?title=Available_System_Properties#gsc.tab=0
glide.ldap.binary_attributes
Comma-separated list of LDAP attributes that should be converted from binary format to encoded64 strings. If you set this property, only the values listed are converted. The most common attributes are objectSID and objectGUID. These converted values are unique and can be used as the coalesce field on the LDAP import mapping. If this property is blank, ServiceNow tries to map these binary attributes without the conversion and they are not guaranteed to be unique since they are not properly converted to string values. You can set this property for a MID Server to import BLOB data through a MID Server, starting with the Fuji release.
|
https://youtube.com/watch?v=zYi8KhP9SUk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2016 02:55 AM
If you're importing them directly into a String field without any modification, are they still in Base64? They should keep the hex value in a string field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2017 03:44 AM
Hi John
Did you find the algorythm to convert BASE64 encoded GUID like AatbntwHoUuoj5M0L0sJJw== to HEX format like "9e5bab01-07dc-4ba1-a88f-93342f4b0927"?
I can decode it from BASE64 using
var guidEncoded = 'AatbntwHoUuoj5M0L0sJJw==';
var binaryData = GlideStringUtil.base64Decode(guidEncoded);
but what do I do next to have it in HEX format?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2017 04:32 AM
I found the following will prevent the field from being modified from the original guid in ldap.
http://wiki.servicenow.com/index.php?title=Available_System_Properties#gsc.tab=0
http://wiki.servicenow.com/index.php?title=Available_System_Properties#gsc.tab=0
glide.ldap.binary_attributes
Comma-separated list of LDAP attributes that should be converted from binary format to encoded64 strings. If you set this property, only the values listed are converted. The most common attributes are objectSID and objectGUID. These converted values are unique and can be used as the coalesce field on the LDAP import mapping. If this property is blank, ServiceNow tries to map these binary attributes without the conversion and they are not guaranteed to be unique since they are not properly converted to string values. You can set this property for a MID Server to import BLOB data through a MID Server, starting with the Fuji release.
|
https://youtube.com/watch?v=zYi8KhP9SUk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2017 05:21 AM
And you got "9e5bab01-07dc-4ba1-a88f-93342f4b0927" at the end? Strange. Does not work for me.