LDAP import from AD to SN - ObjectSID is not the same between systems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2015 12:26 PM
I've spent the last couple hours searching the Wiki and Google for an answer with no luck.
When I use Powershell to query AD for my ObjectSID I get something like this: S-1-5-21-3934281687-3809050549-1115651111-12456
When I look at the ObjectSID in my user record in ServiceNow I see: AQUAAAAAAAUVAAAA11+F6rV/CjPb6MghYtwAAA==
1. Is ServiceNow encrypting the SID?
2. I've read a few times now that it's better to Coalesce on ObjectGUID rather than ObjectSID. Is this a Best Practice?
3. If #2 is correct, is this a simple change or could I be setting up for a big mess?
Thanks in advance Friends!
~ Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2017 11:24 AM
thanks vlor.
Yes, it is in the format of "AQUAAAAAAAUV........."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2017 10:34 AM
hi valor,
i checked the property and its fine, still i am getting the encoded value and not string.
is there any transform script required for this ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2017 10:56 AM
No transform script required. See my other reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2020 08:45 AM
Hi,
I am also facing the same issue.
I also need objectSID in S-1-5-21 format but it is coming in AQUAAAAAAAUVAAAA11 format.
Please let me know if you found a solution for this.