• Resolved wilhud

    (@wilhud)


    Getting an error when clicking on the button to Login using the SSO. It works fine on desktop. The user can login to the first site, click over to the second site, press the login button and it recognizes the user and logs them in fine. However, when using the exact same account on a mobile device, the login button throws a Misdirected Request error. “The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.” Everything is the same as when logging in via desktop. I’m using the same URLs and clicking the same buttons, but getting a different result.

    Any ideas on what this issue might be?

    Thanks,
    Wil

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter wilhud

    (@wilhud)

    Adding some more detail from my digging into this more. The error logs are showing…

    “Hostname provided via SNI and hostname provided via HTTP have no compatible SSL setup”

    One domain is a subdomain of the other. Both are using the same SSL certificate with SANs. Wondering if that is maybe part of the issue. Gonna continue digging.

    Wil

    Thread Starter wilhud

    (@wilhud)

    Turns out it was the AutoSSL in WHM that was causing the conflict. The SSL had both domain names included on one SSL and on mobile it was causing the SNI issue. Once I separated the domain and subdomain to have their own SSL certs, the mismatched redirect error went away.

    Wil

    Plugin Support Sangu Reddy

    (@sangu3105)

    Hello Wil,

    Thanks for reaching out to us.

    It seems like you were able to resolve the misdirected request issue on mobile by separating the SSL certificates for the domain and subdomain.

    Please let us know if we consider this query as resolved.

    If you encounter any further issues related to the WordPress SAML SSO Plugin, please don’t hesitate to contact us.

    Thanks,
    Sangu

    Thread Starter wilhud

    (@wilhud)

    Hi Sangu, yes it seems to have remedied the issue.

    Thanks,
    Wil

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Misdirected Request’ is closed to new replies.