Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 4767

How do we get around this problem where string data being exported to FIM has embedded CR LF?

$
0
0

Hit this oddity when hooking up a customers AD to MIM 2016.

Some of the User Accounts have embedded CRLF in either their streetAddress or description attributes.

When exported to the FIM/MIM MA the Description or StreetAddress attribute of MIM loses a character. It is hard to see just which one.

On a sync from AD I get this (outbound to MIMMA)

Modify Description  OldValue: ABC123<XYZ   New Value: ABC123<>XYZ

Modify StreetAddress Old Value: addressline1<addressline2 New Value: addressline1<>addressline2

I try to represent the screen representation of the unprintable char with the < and > chars above.

I guess these characters are preserved if I was to export that data string to a DataBase, but something fishy is going on in MIM.

How do I prevent MIM from stripping a CR or LF ????

I managed to clean all the telephoneNumbers containing just a single blank which caused an export-not-imported error, but I didn't expect an internal trim.

In the old days, before AD, LDAP v3 street attributes were $ delimited address line so no need for line feeds. I know this is not such a big deal except for the vast amount of unnecessary processing and data transfer.


Viewing all articles
Browse latest Browse all 4767

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>