You are viewing limited content. For full access, please sign in.

Question

Question

Tying LFDS groups to Repository groups

asked on March 26, 2019

I just upgraded a customer from the United license model to RIO.  They have been using Forms for quite a while, and they have about 250 users.  In the process of upgrade, I switched Forms over to LFDS authentication, so I needed to re-create the groups that they had in the repository so they would be available in Forms.  I mirrored the ones in the repository so as to make it easier for them to set up their forms processes again.

In the same vein, I would like to tie the LFDS groups I created with their Repository Group counterparts so user changes in LFDS will carry through to the repository groups and they don't have to go through their entire repository and change all the security to the LFDS groups.

I'm seeing something strange, though.  I have an "Accounting" group in LFDS, and a matching "Accounting" group in the repository.  When I add the LFDS group to the "Directory Server Accounts" node, and go into the properties under Groups, I can see all the Repository groups EXCEPT "Accounting".  Does that mean it has already automatically tied them to each other, or will it simply not let me tie them together because they have the same name?

0 0

Answer

SELECTED ANSWER
replied on March 26, 2019

The naming shouldn't be an issue. Try looking at it the other way around. Go into the Repository Group and look at the linked Trustees.

I usually add LFDS groups to the Repository Groups through the repository group configuration rather than the other way around.

0 0
replied on March 26, 2019

That worked!  Thanks!

0 0
replied on April 6, 2021

I am seeing the same behavior. Are there any other considerations in nesting groups this way? Is it working well for you at this point?

0 0
replied on April 6, 2021

Elexis, I haven't seen any negative effect of setting it up that way, though I haven't had opportunity to follow up with that customer for quite some time.  I can say that it was working well last I heard from them, which was about 18 months ago.

1 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.