• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 94 subscribers
  • Views 2078 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Assigning UNSGroupB to another UNSGroupB doesnt inherit memberships?

qazi.n.akhter
over 5 years ago

Hi, In 1IM 7, I want to establish a dependency between two UNSGroupb objects so if a user gets one, it should implicitly get the other one as well.

I have added this relationship by assigning one UNSGroupB to the other, but it does not affect the memberships. Are there any other configs that we need to to configure?

Any ideas?

Parents
  • 0 over 5 years ago

    There is no inheritance in place that duplicates the memberships when you do group nesting. This works the same as in AD, just because you have group nesting it does not mean that the group memberships will be duplicated.

    If you really need to duplicate the memberships implicitly, you have to implement that yourselve via a custom process chain/script combination I propose.

Reply
  • 0 over 5 years ago

    There is no inheritance in place that duplicates the memberships when you do group nesting. This works the same as in AD, just because you have group nesting it does not mean that the group memberships will be duplicated.

    If you really need to duplicate the memberships implicitly, you have to implement that yourselve via a custom process chain/script combination I propose.

Children