Problem: We're trying to populate HR data from an Oracle source into AD, but there is some concern by mgmt that the attribute we want to use for the key should not be exposed (even though we're putting it in an AD CA).
Proposed Solution: We want to be able to get to the .NET hashing/encryption functions within the context of the Global Script to run a basic encryption hash on this particular attribute, so that it is encrypted in AD. While not a scripting expert myself, I was told that we need to be able to add a reference to the .NET System.Security which contains the System.Security.Cryptography namespace.
DTM Question: I've read the INFO on DTM scripting and am not sure if DTM completely cuts off access to the .NET Assembly References cited (MsCorLib.dll; System.dll; System.Data.dll; System.Xml.dll; System.DirectoryServices;). Am I reading this correctly, and are we thus in fact unable to use the .NET System Security as part of our Global Script? What (if any) are our limitations here and is it possible to run a hash/encryption on an attribute?
Thanks,
ElKabong