LegacySameSiteCookieBehavior

%3CLINGO-SUB%20id%3D%22lingo-sub-2892081%22%20slang%3D%22en-US%22%3ELegacySameSiteCookieBehavior%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2892081%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20this%20%3CA%20href%3D%22https%3A%2F%2Fadmx.help%2F%3FCategory%3DEdgeChromium%26amp%3BPolicy%3DMicrosoft.Policies.Edge%3A%3ALegacySameSiteCookieBehaviorEnabledForDomainList%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Epolicy%20option%3C%2FA%3E%20been%20deprecated%20(for%20allowing%20SameSite%20cookies%20to%20be%20none%2C%20insecure%2C%20etc.).%20As%20of%20last%20week%20our%20users%20were%20able%20to%20perform%20punchout%20over%20HTTP%20with%20cookes%20set%20to%20none%2Flax%20and%20as%20of%20this%20week%20it%20no%20longer%20functions.%20(this%20is%20a%20temporary%20stopgap%20for%20us%20while%20we%20are%20upgrading%20things).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Visitor

Has this policy option been deprecated (for allowing SameSite cookies to be none, insecure, etc.). As of last week our users were able to perform punchout over HTTP with cookes set to none/lax and as of this week it no longer functions. (this is a temporary stopgap for us while we are upgrading things).

 

 

 

0 Replies