You are viewing limited content. For full access, please sign in.

Question

Question

Forms Login Issue-Microsoft Edge (Chromium)

Forms Directory Server Version 10
Updated March 9, 2022
asked on March 18, 2021

Hello,

Customer is trying to move to using Edge Chromium and the users are encountering an issue with the login page, where it just keeps asking for their Windows Credentials and never takes them to their Forms Inbox page.

They are a RIO customer using LFDS with Windows Authentication.

This issue does not occur in Chrome.

Also- Their LF system is hosted in Azure.

Anyone else encountered or encountering this issue?

Appreciate the feedback,

Jeff Curtis

 

0 0

Replies

replied on March 18, 2021

Hi Jeff,

Is it possible they are running into this known issue? https://support.laserfiche.com/kb/1014262/windows-authentication-fails-after-upgrading-directory-server

If so, they should check their application pool identities in the IIS management console to make sure they have the expected values in place.

Best,

Chase

0 0
View 5 previous replies
replied on March 19, 2021

Hey Chase,

Customer tried changing App Pool to use Local System and their Domain LF Service account with no luck.

Should I open a Support Case to further troubleshoot?

Appreciate the feedback,

Jeff Curtis

0 0
replied on March 19, 2021

Sure, opening a support case would be helpful.

0 0
replied on March 19, 2021

Thanks Chase,

Opened the case.

Jeff Curtis

0 0
replied on April 20, 2021

Hello,

 

Would you please let us know what the result of the case is? I am curious if anything can be done to resolve this, or if it is a Edge issue related to this KB:

https://support.microsoft.com/en-us/microsoft-edge/issue-with-blocking-third-party-cookies-f91209bd-0104-2446-61be-d2e4d7da64da

0 0
replied on April 21, 2021

Hi Drew, the case Jeff opened is still in progress. The case number is #216014 for your reference.

0 0
replied on December 16, 2021

Apologize as I did not update this post with the resolution.

Below is the resolution:

Remove Negotiate from the LFDSSTS->Windows Auth->Providers. After doing that it works perfectly in Chrome, Edge, and everything.

2 0
replied on March 7, 2022

We are experiencing this exact issue with the Web Client. We did remove Negotiate as a provider from LFSDSTS Widows Authentication, but clients are still receiving the prompt. Has anyone else run across this issue and/or have any advice?

0 0
replied on March 9, 2022

Hi Alex, you may want to open a support case for this issue so we can get more information.

0 0
replied on March 18, 2021

Thanks Chase

Customer has not updated recently, but I am going to have them check the accounts running both of the App Pools listed in the KB article and try changing them to Local System if they are set to Network Service.

Appreciate the feedback,

Jeff Curtis

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...