Cora SeQuence has a built-in anonymous provider that you can use as a generic authentication provider, or for a specific location. Find the location path you need, or create a new element for it and add this content.
In this example the
runtime.aspx was copied into
runtime2.aspx, and this page now has anonymous access, so users that are not registered in Cora SeQuence can access the runtime pages.
This is useful when you want to enable accessing the first step of the process (form) outside of Cora SeQuence.
<location path="_layouts/runtime2.aspx"> <sequence.engine> <authentication> <providers> <clear /> <add type="PNMsoft.Sequence.Security.AnonymousUserAuthenticationProvider, PNMsoft.Sequence.Runtime, Version=22.214.171.124, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1"></add> </providers> <anonymous enabled="True" username="SequenceAnonymousUser" password="1"></anonymous> </authentication> </sequence.engine> </location>
- You need to create the "anonymous" user manually in the Employees table UI, and grant the user permissions on the workflow/form that they require access to.
- The password in the config file is the same password string that it is saved in tblEmployees for this user. So, depending on the product configuration, it can be either clear text or encrypted.
- You will also need to make the new
RunTime2.aspxpage in IIS accessible to the anonymous user. From the page's Authentication settings, enable anonymous access.
If you want to make a Web service listener anonymous, you need to create a real file (it could be a notepad file) with the same name as the Web service listener, for example,
myListener.asmx. Place the file in the
SequenceServices folder, and in the IIS set the file authentication to anonymous.
There are two
SequenceServices folders, one in the Flowtime and one in the Administration. If you are using both end points, repeat the steps for both sites.