Question

How do we restrict external 'public' to Internal 'public' Forms using 2 Forms Portal Licenses?

Forms

Updated February 8, 2018

asked on February 7, 2018

We have a client that has just purchased a 2nd Forms Portal License for the purpose of publishing internal forms without the need for a named user license/participant license.

They did not want external users the possibility to stumble upon or fish out their 'internally' used forms.

The problem we have is when they now are able to make their internal forms 'public internally' it still makes the form public 'externally'.

How can they toggle the form to be public on their internal forms server but stay 'restricted' on the DMZ Forms server?

We are using the same Forms database internally and on the DMZ so that we can have the internal forms server take over any processes that are started from the DMZ (by the public).

1 0

Replies

replied on February 7, 2018 • Show version history

Shaun, the only way I would think you can do it is to separate the two servers so that they are acting independently. My understanding of how Forms works is you either have a form that has access rights for a Named User, or you have one that requires no authentication. I don't think you have a choice of deployment once you pick "no authentication," beyond putting those "internal-public" forms on a separate Forms deployment entirely. This of course prevents you from sending your "external-public" forms to the internal server for processing from there.

If they weren't worried about someone trying random URLs to find internal-public documents, I'd just say create a separate "selective" landing page for the external-public documents for the DMZ-based server and call it good. We also use a field-based authentication for our internal-public forms that requires the person creating the form enter the last 4 of their social and their payroll ID. If there's a mismatch, we would, in your scenario, immediately terminate the process.

0 0

replied on February 8, 2018

We have the same setup, internal and DMZ forms servers sharing a database. On our DMZ server, for the internal only public forms, we deny access to those in the IIS Manager under the request filtering rules. It's the only solution that we have come up with to restrict the access.

~ Andrew

0 0

replied on February 8, 2018

Thank you Scott and Andrew.

Andrew, we did give our client that option that you did, but they thought it would be one step better to have their own portal inside. I just thought (as well as the client and everyone on my team) that we would be able to share the database still but make the form restricted on the DMZ but make it public on the internal DMZ. Maybe the only way to do this is by NOT sharing the same database? Laserfiche, I would appreciate your input on this.

Thanks

0 0

You are not allowed to follow up in this post.

Question

Question

How do we restrict external 'public' to Internal 'public' Forms using 2 Forms Portal Licenses?

Replies

Sign in to reply to this post.