Our AD includes both internal and external users. We are not forested or federated for external users, we've simply created external users in our AD for authentication purposes. To illustrate this, if our domain is 1LOCAL, an internal user account is 1LOCAL\janedoe, while an external user account is 1LOCAL\johndoe@email.com.
We've assigned named user licenses to both internal and external users in our Laserfiche Directory Server. Trust is established for each user type in the Windows Account section of our Production repository. Named users are synchronized to Forms, and I can see both internal and external user accounts. Using the previous example, I can see both 1LOCAL\janedoe and 1LOCAL\johndoe in the "Named Users" section of Forms.
Here is the rub, internal users can successfully authenticate into Forms, but external users cannot. Using our example, we've tried logging in as:
- johndoe
- johndoe@email.com
- 1LOCAL\johndoe
- 1LOCAL\johndoe@email.com
None of these work. The odd part is, johndoe can login to WebLink using 1LOCAL\johndoe. This issue appears to be isolated to Forms (we are using Forms 9.2.1 in production). Additionally, we installed Forms 10.2 on a different server, configured and sync'd, and johndoe was able to login as johndoe@email.com. So maybe this issue is isolated to Forms < 10?
Any ideas on what is causing this? Anybody run into similar issues? Is there a way we can program a custom login module for Forms to get around this behavior?
We are using Directory Server 10.0.0.270, Forms 9.2.1.1088, and Server 9.2.0 build 343 in Production.