0 votes

We are using the SeeAlso attribute to store who is responsible for specific accounts.

We do not wish to use the Manager field, because the Manager/Direct Report structure is reflected in org charts in many applications we use.

So we implemented the SeeAlso attribute to store the DN of the "Account Owner"

The only bit we are missing is to grant permissions to edit a user when the initiatior DN is present in the SeeAlso attribute. This way, if my DN is present in the SeeAlso attribute for a user, I have rights to, for example, extende the expiration date of an account.

Is that possible?

by (310 points)

1 Answer

+1 vote
by (169k points)
selected by
Best answer

Hello Manuel,

Yes, it is possible using a dynamic Business Unit and a Security Role. For each user the Business Unit will contain only the accounts that have them specified in the See Also property and will be used to assign the Security Role. For information on how to create dynamic Business Units, have a look at the following tutorial: https://www.adaxes.com/tutorials_ActiveDirectoryManagement_CreateDynamicBusinessUnit.htm. On step 3 of the guide, select Query Results and enter the following LDAP filter into the corresponding field: (&(sAMAccountType=805306368)(seeAlso=%distinguishedName%)) image.png The Security Role will look like the following: image.png Additionally, you might consider using the Assistant or Secretary property to store managers. In this case, you will not need a Business Unit and the Security Role will look like the following: image.png

0

Thank you very much, this solves it.

We wish to use the SeeAlso because it allows multiple values to be used (so that multiple users can have permissions over multiple objects).

This worked perfect as you suggested

+1

Hello Manuel,

Thank you for the confirmation.

For you information, the Secretary property is also multi-valued, so you might consider using it to store multiple managers and avoid using the Business Unit.

0

I wasn't aware Secretary is also multi-valude. Great info, thanks!

0

After giving it some thoughts, using the Secretary field makes sense, considering that is also multi valued.

I am a little confused by the example you show, where the permissions show the Trustee to be "Assistant". Shouldn't it be "Secretary"?

image.png

+1

Hello Manuel,

Yes, you are absolutely right. It was just an example on how you can use either of the security principals. According to your screenshot, the Security Role should work just fine.

Related questions

0 votes
1 answer

Dear Is it possible to change the values of a custom attribute (adm-CustomAttributeTextMultiValue4) when selecting a value from another custom attribute (adm-CustomAttributeText1). For ... , 2Latijn, 3Latijn, etc... Is this possible? Sincerly Hilmi Emre Bayat

asked Aug 26, 2019 by hilmiemrebayat (510 points)
0 votes
1 answer

So we have a new domain , lets say @def.com. It's within our primary domain @abc.com...this was done due to a company split. What changed for our users were their ... operational. LDAP Server unavailable" If I use my @abc.com, it works. Please advise. thanks

asked Oct 1, 2013 by MeliOnTheJob (10.6k points)
0 votes
1 answer

How do change the display name of a custom attribute in version 2017.2? All the information I am finding contains links that bring me to 2018 version

asked Nov 1, 2018 by hgletifer (5.4k points)
0 votes
0 answers

Before Deactivation of an Account on the Webinterface our Help Desk need to change the AD User Description manually. Is it possible to force a manual change before deactivation ?

asked Feb 7 by lv01 (250 points)
0 votes
1 answer

We created a Scheduled Task and chose our user organisational unit as the activity scope. Then we realized that only about 10 % of the users are object-type: user and 90 % object- ... s no option in adaxes. But there is one for the object type User. Why that ?

asked Dec 5, 2019 by PGstoehl (490 points)
2,087 questions
1,855 answers
5,220 comments
1,942 users