You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 19, 2021. It is now read-only.
After successful authentication at WSO2 and POST back to /auth/saml/callback on the backend, WSO2 seems to trigger a condition that causes the browser to set Origin to null:
then you are going to run into trouble if the browser doing the POST from the id.eapp.local.test context is not setting Origin.
My intuition is that once this issue gets deep-dived, the approach to single-sign on might have to be re-visited in order to get CORS set up properly – perhaps switching to one of the other SAML profiles or WSO2-supported protocols.
After successful authentication at WSO2 and POST back to
/auth/saml/callback
on the backend, WSO2 seems to trigger a condition that causes the browser to set Origin to null:This affects the
CORS
setting and might be caused by the privacy contexts listed here:https://wiki.mozilla.org/Security/Origin#Privacy-Sensitive_Contexts
The text was updated successfully, but these errors were encountered: