Produce FAQ

Enabling anonymous or guest access (external forms) in Infiniti

For some Infiniti solutions, Produce is configured to allow anonymous access to publish forms, often via an existing website. Generally, users are navigated directly to a web form or wizard and do not know they are interacting with Infiniti.

Anonymous access is achieved by configuring the Guest account in Manage once an anonymous license key has been provided.

Once the guest account has been configured, users that access Produce will be granted access as described in the table below depending on the authentication type used.

How to enable guest access (Manage)

1. Navigate to Licensing and provide an anonymous access key.
2. Navigate to users and view the user ‘Guest’ properties.

• Uncheck the guest account checkbox.
• Click on Security and add the user to any appropriate groups or roles as required.

URL Structure

URLs that point directly to an Infiniti form contain the TemplateGroupGuid as per the following example:

http://server/infiniti/produce/wizard/YOURGUID

http://prodserver/infiniti/produce/wizard/bc825d12-e97f-41a0-b709-e3ece8deb30c

Alternatively, you can access the Infiniti project directly via a simple link, refer to Accessing Infiniti Forms Directly article for a guide on how to do this.

Configuring Guest Access for Windows Authentication (v10.0.30 +)

IIS Manager
On the virtual directory for Produce, select Authentication and enable "Anonymous Authentication" along with the existing "Windows Authentication" item.

Produce
Add a new setting to appsettings.json -

"Authentication": {
  "Windows": {
    "ReplaceIdentity": "True"
  }
}

Guest user access has to be enabled as normal through Infiniti Manage - click here to see how.

On first browse to Produce you will get guest access like you normally would with forms authentication. When you click Login or attempt to access a project the guest doesn't have access to you will be logged in with your Windows credentials.
Windows Impersonation doesn't work with configuration.

🚧

Note: API access under Windows authentication

It may be tempting to partially configure a Windows-authenticated Produce environment for Guest access in order to allow access to the API. Such a configuration would enable Anonymous authentication in IIS but not enable the Guest user or the appsettings "ReplaceIdentity" option. This allows requests from the Send To REST Service action to reach the API using a service account's credentials (and without inheriting the credentials of the user running the form). Unfortunately the lack of Guest and ReplaceIdentity causes problems with other user credentials being applied to the REST action's execution. A more stable solution is to set up a second Produce environment with Forms authentication and the same database connection string, and use that instance to interact with the API.