Unity client is prompting some users for login when opening document

[Timothy_Hood]

I have a couple users, and myself, that are getting prompted to enter their network credentials when accessing a Unity form document in the Unity client. This doesn't occur with scanned documents, only Unity forms. The following window pops up, "connecting to {appserver}". When credentials are entered, the user can continue to access Unity form documents as normal. If they close and reopen Unity, they get prompted again when accessing the first Unity form, whether they previously checked "Remember my credentials" or not. If they cancel without entering credentials, they get an error "401 - Unauthorized: Access is denied due to invalid credentials."

Interestingly enough, this previously occurred to me on OB13 with Windows 10, now we are are 16. Only recently has it started to occur with our normal users, but only two so far. They have the exact same rights and permissions, PC OS and software versions, and received the same install via GPO login script as other users who do not experience this issue.

[Joe_Roche]

Tim,

Thank you and Rich for your time yesterday to troubleshoot this issue.  In this case the root cause was lack of trust between Internet Explorer and the appserver.  The solution is to add the appserver URL to the browser's Local intranet zone and restart the Unity Client.

Regards,

Joe Roche, IT Support Specialist, Integra PaperLESS Business Solutions

[Doug_Kupec]

hi Joe,

The issue is occurring with the configuration of the Application Server for using Windows Authentication on all entry points into the Application Server. What I would suggest using is Web Application Management Console (WAMCon) and run the Optimize for Windows Authentication utility on the Application Server.

This will only configure the files that need Windows Authentication while using Anonymous Access for all other requests. This will prevent IIS from requiring authentication when accessing a Unity Form.

Hope this helps,

Doug

PS. If it looks like Optimize has already been executed against your Application Server, manually disable Windows Authentication through IIS Manager and relaunch WAMCon and attempt to run it again.

[Dave_DeJonge]

Doug thanks for the post, I was unaware of the optimize option. I found this white paper, dated from 2015, that give a bit more detail on what the optimize option actually does. (pg 33 - 38)

https://www.onbase.com/community/technical_communities/security/m/downloads/19185?forcedownload=true

my question to anyone is, Is this information still relevant for v15 and above? Dave

[Doug_Kupec]

hi Dave,
Yes, that document is generally still accurate. Adam Shane added it to the review back log to ensure enhancements in versions 16 and 17 are noted in the document.

thanks,
Doug