This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SingleSignOn SameSite Attribute

Hi,

if there is a web application which uses SSO for authentication, we get a cookie container object after the request of the WebServiceSSO.aspx.

In our constellation the web application is hostet at another domain. Because of that SSO doesn't work. In the cookies is the SameSite attribute set, so all modern browsers block the SSO because of the different domain.

Is there any possibility to solve this? Is there any configuration which can affect the same site attribute?

Greetings

Michael
  • Hi Michael,

    I'm not sure I understand the architecture here.

    Do you have users making a HTTP request to WebServiceSSO.aspx directly, passing that cookie to a web application, and the web application is attempting to use it? Or is the user logged in with SSO to the web application, which then makes a request to WebServiceSSO.aspx, and then... Who's trying to use the cookie?

    Regards,

    Craig.
  • Also, just to highlight that as a partner you have a support team who might be best placed to help. It is likely that queries like this would end up with me, but it's probably better to follow that process than it is to use this forum.

    Regards,

    Craig.

  • Hi Michael,

    I'm not sure I understand the architecture here.

    Do you have users making a HTTP request to WebServiceSSO.aspx directly, passing that cookie to a web application, and the web application is attempting to use it? Or is the user logged in with SSO to the web application, which then makes a request to WebServiceSSO.aspx, and then... Who's trying to use the cookie?

    Regards,

    Craig.


    If you tell me the correct way, I can tell it to our customer.
    As far as I know, they are making the request inside the web application. But the application is not hostet at the same domain as M-Files.
  • I'm not sure there is a "correct answer" here, as it depends largely on the architectural setup. What I think you probably have is this:


    • User connects to web application A via SSO. Web application A knows the user it's running as and can access things like the user's name and email and things.

    • Web application A attempts to make a connection to MFWS using SSO.

    • Requests to MFWS fail due to authentication issues.



    In this case what's probably happening is related to the double-hop problem whereby the Windows credentials can only be used on web application A, and not used to subsequently authenticate to a second machine. This isn't something I've ever had to configure myself (it's outside of the direct context of either the development aspect of the integration and also the M-Files implementation), but my understanding is that the solution involves configuring the authentication to allow delegation. In this case you probably need to speak to someone who understands authentication providers far better than I.

    But I may be completely wrong in my assumptions, hence my question.

    Regards,

    Craig.