Consider the following scenario:
- Deployment:
- Internal Forms server (primary forms server), on internal network, server within AD domain.
- Public Forms Portal server, in DMZ, server not in the domain.
- Form/Business Process
- PUBLICLY accessible (anonymous submission via the Forms Portal server)
- After submission, an email is sent to a Forms user that is an AD user (has a named user license, synced from repository to Forms).
Question...
When viewing the Forms Portal user list, it's unable to resolve domain user accounts SIDs to usernames because it doesn't have access to AD.
My concern is when the business process reaches step 2, if it's performed by the Forms Routing Service on the Forms Portal server (where it was originally submitted from), then it won't be able to perform the AD lookup for the user's email address (since the Forms Portal server isn't in the domain).
For Forms/Business processes submitted on the Internal Forms Server, everything will work fine. But I'm concerned about what may happen with a Form submitted through the Public Forms Portal server requires some AD lookup somewhere in the business process... or is this somehow offloaded over to the Internal Forms Server (because it's been configured as the primary forms server).
We haven't tested this specific scenario, but we're about to deploy this implementation and I'm trying to be prepared to ensure I understand this particular aspect/functionality.
Thanks!