Hi Reneilwe Seshoka,

I am having the same issue, did you ever find a solution?

Have you seen this KB article? https://support.laserfiche.com/kb/1014094/additional-configuration-for-chrome-80

Has there been a fix for this yet?

I had this issue and was able to update the outboundrules.config to allow the login to work, but I have a couple of issues with it.

 
<outboundRules>
  <rule name="Set SameSite to None in the middle">
    <match serverVariable="RESPONSE_Set_Cookie" pattern="(.*)SameSite=([a-zA-Z]+);(.*)" negate="false" />
    <action type="Rewrite" value="{R:1}SameSite=None;Secure;{R:3}" />
  </rule>
  <rule name="Set SameSite to None at the end">
    <match serverVariable="RESPONSE_Set_Cookie" pattern="(.*)SameSite=" negate="false" />
    <action type="Rewrite" value="{R:1}SameSite=None;Secure" />
  </rule>
  <rule name="Add SameSite if it does not exist">
    <match serverVariable="RESPONSE_Set_Cookie" pattern=".*"/>
    <conditions logicalGrouping="MatchAll">
      <add input="{R:0}" pattern="(.*)SameSite=" negate="true"/>
    </conditions>
    <action type="Rewrite" value="{R:0}; SameSite=None;Secure" />
  </rule>
</outboundRules>

After Samesite=None, we added the ;Secure , once added it now allows us to login through the iFrame, but it navigates to the top level folder instead of the client folder link they had selected and still gives the red warning message at the login page. If the navigate back to the client folder links after the initial login, it does work as expected.

Any suggestions to get it routing to the proper folder the first time the link is clicked and/or removing the warning message in the iFrame?