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

Question

Question

Can only add users from the repository in formsconfig to process modeler tasks?

asked on December 18, 2018

Hello,

 

Just wanted to see if I'm on the right track here. We have a customer with 4 repositories. They have Forms Professional, and use Forms to submit to at least 2 of the repositories. However, we've just run into an issue involving sending an email to a user who isn't listed as a Windows account in the repository we have in the User Authentication tab in forms config. I'm sure we could type out the email address instead of the user account and it would work just fine, but I wanted to verify that we'll only be able to select Windows accounts in the process modeler for any kind of task if that Windows account is listed in the repository that we setup authentication to in formsconfig.

Thanks!

0 0

Answer

SELECTED ANSWER
replied on December 18, 2018

Correct. Forms syncs its users based on the repository specified in FormsConfig. Only the Windows accounts that sync to Forms are accessible in the process modeler. You can use email addresses to send emails out to anyone. 

If you have a Rio system, LFDS authentication would allow you to use the same set of users across multiple repositories and Forms. 

0 0
replied on December 18, 2018

Got it. We'll look into LFDS authentication as this is a Rio system.

 

Thanks!

0 0
replied on December 18, 2018 Show version history

I highly recommend the LFDS route. The switch will take a little work and you need to run a SQL query on the Forms db to enable the option (obviously back everything up first), but it is worth the effort.

Since we switched, we've been able to connect AD groups to LFDS groups, which we then use to grant access to Forms, and repository folders. It is way more centralized and very easy to manage. SSO makes life so much easier too.

1 0
replied on December 18, 2018

Is this what you had to do?

0 0
replied on December 18, 2018 Show version history

Yes, but I would check FormsConfig to see if the option is already there first.

0 0
replied on December 18, 2018

Do you recall this change breaking any of your forms processes? Or was it all good to go once you successfully made the change in formsconfig?

0 0
replied on December 18, 2018 Show version history

It was a very smooth transition. It really only took 5-10 minutes to make the change and check that it synced the users properly.

We backed up the db just in case things went wrong, and we also had LFDS fully configured ahead of time so we didn't have any issues with users being lost.

In LFDS we created a group called Forms, then nested all the other directory/AD groups inside of that parent group.

As soon as the authentication type was changed we used the LFDS Forms group we created to provide access to the application in FormsConfig.

0 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.