CustomAttribute to Manager DN

Question

Hello,

We have a workflow where we get the manager name via our HR system. I am putting this into a customattribute.

As the name pulled from HR is in the form of firstname lastname and the manager attribute cant handle this.

I would like to utilize Adaxes to take the customattribute1 (example) and modify it to a DN and put it into the target user manager field.

Is this possible? If so; how?

Comments

Hello,

Sorry for the confusion, but we are not sure what exactly you mean. Do you need to take the first name and last name of a user from a user property, find the corresponding user account and set them as the user manager? If that is correct, what should be done if there is more than one user with the specified first and last name found?

Any additional details and live examples of the desired workflow will be much appreciated.

---

Let me try and make it more clear, we get our Manager property from our HRM system via an API.

This value is "Firstname Lastname" feeding this directly into the manager property cant be done as the manager property within AD requires the DN name and not the Firstname Lastname of the object.

So we would like to feed the value from the API into the customattribute15 (example) and then from there get Adaxes to look at this and "translate" it to the DN.

If more then one user with the same firstname and lastname is there then that could be a problem I havent thought of yet.

We could also use the WorkerID (value from HRM) instead of firstname/lastname and translate that to the object in AD in the same way I guess.

---

Hello,

So we would like to feed the value from the API into the customattribute15 (example) and then from there get Adaxes to look at this and "translate" it to the DN.

Should the DN replace the custom attribute value? Alternatively, the DN can be directly passed to the Manager property and the custom attribute will be cleared.

We could also use the WorkerID (value from HRM) instead of firstname/lastname and translate that to the object in AD in the same way I guess.

Any value that is unique in all the domains managed by Adaxes will work just fine. However, we still need to know what should be done in case of duplicates being found.

---

Passing it to the Manager property and not clearing the Custom Attribute will be fine.

Incase we use the WorkerID there should not be a duplicate ID. The ID is unique.

Answer 1

Hello,

Thank you for the confirmation. Here is the script you can use. It can be executed in a business rule, custom command or scheduled task configured for the User object type. In the script:

• $propertyStoringManagerID - Specifies the LDAP name of the user property (customattribute15 in your example) storing the identity of the manager to be set.
• $managerIDPropertyName - Specifies the LDAP name of the manager property (WokerID in your example) that should be equal the identity stored in the corresponding user property.

$propertyStoringManagerID = "adm-CustomAttributeText15" # TODO: modify me
$managerIDPropertyName = "employeeID" # TODO: modify me

# Get manager ID
try
{
    $managerID = $Context.TargetObject.Get($propertyStoringManagerID)
}
catch
{
    $Context.LogMessage("Property $propertyStoringManagerID is empty.", "Warning")
    return
}

# Search parameters
$searcher = $Context.TargetObject
$searcher.SearchFilter = "(&(sAMAccountType=805306368)($managerIDPropertyName=$managerID))"
$searcher.SearchScope = "ADS_SCOPE_SUBTREE"
$searcher.SizeLimit = 2
$searcher.ReferralChasing = "ADS_CHASE_REFERRALS_NEVER"
$searcher.VirtualRoot = $True

try
{
    # Execute search
    $searchResultIterator = $searcher.ExecuteSearch()
    $searchResults = $searchResultIterator.FetchAll()

    if($searchResults.Length -eq 0)
    {
        $Context.LogMessage("No user found with $managerIDPropertyName set to $managerID.", "Warning")
        return
    }
    elseif($searchResults.Length -ge 2)
    {
        $Context.LogMessage("Found 2 or more users with $managerIDPropertyName set to $managerID.", "Warning")
        return
    }

    # Update the user
    $managerDN = $managerDN = $searchResults[0].GetPropertyByName("distinguishedName").Values[0]

    $Context.TargetObject.Put("manager", $managerDN)
    $Context.TargetObject.SetInfo()
}
finally
{
    # Release resources
    if ($searchResultIterator){ $searchResultIterator.Dispose() }
}