DocumentViewer does not work if third party cookies blocked in cross domain
Question asked by vishnani karan - 10/16/2020 at 8:19 AM
Users get the session expired error when the third party cookie is blocked when used documentViewer in cross-domain. 

Is the cookie necessary for the document viewer, as in some browsers the third party cookies are disabled, and also in incognito mode the third party cookies are disabled? This affects the end-users as end users don't have much knowledge and use the case of the cookies.

Is there any workaround other than using the cookie?

Waiting for your reply on this.


2 Replies

Reply to Thread
Cem Alacayir Replied
Employee Post
If you are using an iframe and cross-domain url, see the announcement here:
Cem Alacayir Replied
Employee Post Marked As Answer
With FileUltimate v7.8.1 and DocumentUltimate v5.8.1 (November 23, 2020 updates), this issue is fixed out of the box for both ASP.NET Core and ASP.NET Classic (no settings required):

  • Added: Cookieless session will be used when necessary to automatically fix session issues, i.e. when the browser
    does not allow cookies via browser settings or via iframe with a cross-domain URL.
    The cookieless session will be established via headers, form or querystring where possible.

    Added GleamTechWebConfiguration.AutoCookielessSessionEnabled property to control this feature (default value is true).
    You don't need to use GleamTechWebConfiguration.CookieSameSiteFixEnabled when this property is true.

  • Fixed: When <sessionState cookieless="true" /> was set in Web.config, the below error was being thrown:
    'Invalid method request: Method with name "" not found'

Reply to Thread