Allow the script to handle LDAP names containing a space when adding safe permissions

[Francesco-f7o]

Issue

When using the script to manage safe owners, if the user location is an LDAP integration that contains a space in the name, the management doesn't work, as the script seems unable to handle a location that contains a space.

This may happens in legacy deployments or in scenarios where the name for the LDAP integration has been left to its default (which is indeed "LDAP integration").

Unfortunately this integration name cannot be updated, as explained here: .

Desired solution

If the script could handle the existence of a space in the MemberLocation field of the safe-members-sample.csv, it could be used for those environments where the directory name was set with a space and cannot be changed any more.

Alternatives considered

We tried to populate the field using some escape characters, such as " or ' or ` before the space to escape it, but without success.
The simplest alternative we found to this approach is to revert to psPAS, which works fine with a directory name that includes spaces, but it's not able to consume a CSV file out of the box as this script does, which is why this would be considered approach.