No, the fix requires redesigning parts of the authentication as Windows authencation credentials don't work across untrusted domains. It is not something that can be hotfixed at this time.

So is this something 9.3 will provide?

Most likely 10, not 9.3.

Wow...so what is a customer supposed to do when they can't upgrade to 9.2 per the recommendation of Laserfiche for other issues they have with Forms?  We've been sitting on 9.1 due to the Domain issues...but other issues have arrived that we've been told are fixed in 9.2, but we obviously cannot upgrade.  What is the ETA of 10?

Daryl, this is not a bug, it's an enhancement request. Windows authentication in Forms has never worked across domains that do not trust each other. If there are other domain issues you're referring to, they're probably best handled through support cases.

Miruna I am not following what you are saying here.  Currently our Forms 9.1 server can talk to our Laserfiche server.  They both reside in separate domains.  With nothing else changing but an upgrade to 9.2, the forms server can no longer talk to our Laserfiche server.  I don't understand what windows authentication has to do with this. 

Miruna,

I'm confused...this worked in Forms 9.0 and 9.1...so why would it be an enhancement?  Tech Support when this issue was first created, considered it to be a bug and therefore, put in an SCR?  You're now saying it's an enhancement and not a bug...but why did this "enhancment" work before 9.2?  To me it would be a bug.

"SCR" stands for "Software Change Request" and it is out internal way of tracking issues. It applies to both bug reports and feature requests. Tech Support filing one does not imply in any way that a hotfix is pending.

The issue report mentioned above in this thread (89247) refers to logging into Forms with Windows Authentication when the Forms and Laserfiche servers are on different domains.

If that's not what you were talking about, then please open a support case so it can investigated separately.

We did open a support case....they created the SCR89247. Again...it works now in 9.1 and it worked in 9.0, it does not work in 9.2. Doens't seem to me that it would be a Software Change Request as we're simply asking that it do in 9.2 what it can do in 9.0 and 9.1...

Daryl, I think the reason for the SCR is because currently in 9.2 it does not work. So a software change is required to get it working. The software has to be changed from the current code to add that functionality back into the system since it was removed or broken in 9.2.

Which is fine...but why would it then be expected that it be fixed in 10 and not 9.3.  Seems odd to take something out that was previously in.  Explain that to an end user paying thousands of dollars for support when their only solution is to use the old software.

The Forms team is looking into it. It looks like your case may have been incorrectly classified as the same issue as the one reported in 89247.

Any updates on this?

Any updates to this case as customer is still sitting on Forms 9.1 and wants to know if this issue will be fixed in 10?