Hi, Everyone I am trying to incorporate security on feeds that are b

siddharthg521 over 11 years ago

Hi, Everyone

I am trying to incorporate security on feeds that are been posted to tempo.My objective is that only those users should be able to see the feeds on tempo that are been stored in process variable (pv!users) .If that process variable is updated and any user is removed or added than the users in that updated process variable must only see the feeds related to that process.(Removed users should no longer see the feeds and newly added users should see the respective feeds.)

When I am passing togroup(pv!users) to the viewers group of "Post feed to Tempo" Smart service, irrespective of who are the users present in the process variable, all users are able to see the feeds on tempo.

I have also tried to use "Tempo Audience Group" that is by default present in People Tab, and have passed in Viewers group of Smart service, but that will create a group for each instance of my process at root directory of Groups.

Hence, along with the abov...

Discussion posts and replies are publicly visible

Parents

0 siddharthg521 over 11 years ago

@abhishek: I am expecting atleast 20 instances to be spawned for my process every day, which counts to approx 600 instances in each month and 7200 instances in an year, which I think is not a good option for doing so.

However the option which you have suggested was not working out.When I am creating a group (as a subgroup) for each instance spawned with Parent group as "Tempo Audience Group", then the group created is not inheriting the security from the Parent Group - "Tempo Audience Group", and hence irrespective of lists of those users who are present in the group, all the users are still able to access the respective feeds.

However if I dont create a group with parent group as "Tempo Audience Group", and simply pass the "Tempo Audience Group" in the Viewers group of Tempo smart service, then it works fine, but again it will create separate group at root for each instance spawned.That is, approx 7200 groups AT ROOT, for just my process, which is not at all a best practice.

Can you please throw some light on it??
Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 siddharthg521 over 11 years ago

@abhishek: I am expecting atleast 20 instances to be spawned for my process every day, which counts to approx 600 instances in each month and 7200 instances in an year, which I think is not a good option for doing so.

However the option which you have suggested was not working out.When I am creating a group (as a subgroup) for each instance spawned with Parent group as "Tempo Audience Group", then the group created is not inheriting the security from the Parent Group - "Tempo Audience Group", and hence irrespective of lists of those users who are present in the group, all the users are still able to access the respective feeds.

However if I dont create a group with parent group as "Tempo Audience Group", and simply pass the "Tempo Audience Group" in the Viewers group of Tempo smart service, then it works fine, but again it will create separate group at root for each instance spawned.That is, approx 7200 groups AT ROOT, for just my process, which is not at all a best practice.

Can you please throw some light on it??
Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data