put() method not executing at all in script

Question

Hi I am trying to utilise the ADSI more and srver side scripting as an attempt to gain a wider knowledge and understanding of the Adaxes objects and interfaces.

I have created a scipt to run after a business rule is triggered but it never seems to execute the put() method.

I understand that ther is a cache and that I need to get() the properties that I want to execute on which I am doing in my script.

The script is intended to handle username and name changes upon approval after the user has changed "sn"

if ($Context.IsPropertyModified("sn"))
{
    $modifiedlastname = $Context.GetModifiedPropertyValue("sn")

    $newValue = $modifiedlastname.Trim()

    $Context.SetModifiedPropertyValue("sn", $newValue)




    Try 

    {
        $adspath =  $context.TargetObject.AdsPath
        $adspath | out-null 

        $user = $Context.BindToObject($adspath)
        $user | out-null

        $firstname = "%givenName%"
        $firstname | out-null
        $sn = $newvalue

        $fullname = "$firstname $sn"
        $Username = "$firstname.$sn"
        $fullname | out-null
        $username | out-null

        $propertynames = $Context.TargetObject.GetInfoEx(@("samaccountname","userprincipalname","mail","displayname","cn"), 0)
        $propertynames | Out-Null

        $context.targetobject.Put("samaccountname",$Username)
        $context.targetobject.Put("userprincipalname",$Username+'@domain.com')
        $context.targetobject.Put("mail",$fullname+'@domain.com')
        $context.targetobject.Put("displayname",$fullname)
        $context.targetobject.Put("cn",$fullname)

        # Commit to the directory
        $user.SetInfo()

    }
    catch
{
    $Context.LogException($_.Exception)
}

}

Answer 1

Hello Will,

The changes are not applied because the Put method is called for the TargetObject property, but the SetInfo method is called for the $user variable. Despite the fact that the same user is referenced by TargetObject property and the $user variable, these are considered different objects in terms of PowerShell. Moreover, there is no need to additionally bind to the user as the TargetObject property of the $Context variable already represents an instance of the user object on which the script is executed.

As far as we understand, you need to change property values once the user last name has changed. If so, there is actually no need to use a PowerShell script. It can be done using a business rule triggering After updating a user. The rule should look like the following:

If you still need to update property values using a PowerShell script, you can use the approach like the following:

$fullName = "%firstname% %lastname%"
$userName = "%firstname%.%lastname%"

try 
{
    # Update property values
    $Context.TargetObject.Put("sAMAccountName", $userName)
    $Context.TargetObject.Put("userPrincipalName", $userName + "@domain.com")
    $Context.TargetObject.Put("mail", $userName + "@domain.com")
    $Context.TargetObject.Put("displayName", $fullName)
    $Context.TargetObject.Put("cn", $fullName)

    # Save the changes
    $Context.TargetObject.SetInfo()

}
catch
{
    $Context.LogMessage($_.Exception.Message, "Warning")
}