MicrosoftBut in this case, this is common practice that you need to ESCAPE the comma if that is part the relative identifier, like CN of the object.
So the example of:
CN= Smith, Billy Bob ,OU=Accounting,OU=Users,DC=Silliness,DC=com
Would look like this escaped:
CN= Smith\, Billy Bob ,OU=Accounting,OU=Users,DC=Silliness,DC=com
And now we would no longer get any Invalid DN Syntax, as this works for just about any application that s using LDAP to access the object.
So this is nothing new or strange behavior.
The really sad part here is, that if you already have code to identify this comma in the relative identifier part, ie like in this example, the CN part, then you are almost done, just escape that comma! And we would not have this problem...
I try to avoid to use SETSPN because of this.
