Rssinclude not updating
After the surrogate expires, the user is sent through the SAML authentication A normal HTTP request is able to complete SAML authentication, but there are some reasons why this might not always complete successfully when using the explicit proxy access method (and therefore cookie surrogates).
Reasons may be (but not limited to): To mitigate this issue, the Web Security Service only redirects a user for SAML authentication if the request came from a Mozilla or Mozilla-compatible browser (Internet Explorer, Firefox.).
In the days of olde, people who wanted to stay in touch with their favorite blogs had to bookmark the site’s URL and visit daily to check for new content or updates. Wouldn’t it have been easier if those people could have simply asked their favorite websites to send out a notification when they posted new content? A feed, also known as an RSS (Really Simple Syndication or Rich Site Summary), is a great way for bloggers to boost readership, make their content more accessible and help readers stay in the loop.
Because of this, feeds are a great way to get your content out to people who may be too busy or otherwise engaged to interact with it.
Loading external content fails with SAML enabled.activate.; Netsupport activation/registration URL.
Activation fails with SAML enabled.clientconfig.microsoftonline-p ; Required for MS Lync activation after first installation.; Effective TLD (cannot set domain wide cookie for sub-domains).; Effective TLD (cannot set domain wide cookie for sub-domains).uk ; Effective TLD (cannot set domain wide cookie for sub-domains).; Embedded images (hot linked) do not follow the SAML ; Kaspersky anti-virus dell.com/Published/Data ; Dell System Analysis Software.; Effective TLD (cannot set domain wide cookie for sub-domains).; Effective TLD (cannot set domain wide cookie for sub-domains).; Effective TLD (cannot set domain wide cookie for sub-domains).mt0.; JSON request from browser embedded Google maps application fails to present SAML session cookie, resulting in redirect loop and failure to load map.; Google Chrome Web Store - not following redirects to SAML SP.hp5.a.; Browser does not provide SAML cookie for TTF and WOOF (Icon files) loaded through CSS.c64.; Browser does not POST the assertion to this domain.layout.; Browser does not provide SAML cookie for TTF and WOOF (Icon files) loaded through google.com/maps/vt ; XML query for map data - not providing SAML cookie within Google Maps preventing map data from loading.
If you have enabled SAML authentication under your Web Security Service (Threat Pulse) account, you might have identified some internal applications are unable to complete SAML authentication and might therefore have stop working as expected.
As of the Web Security Service 184.108.40.206 update on November 1, 2015, this KB is now only relevant to the EXPLICIT proxy access method because the issues and resolution described here relate to how SAML transactions work with 'cookie surrogates':- Explicit access method utilizes 'cookie surrogates'- IPSEC access method now utilizes ' IP surrogates' (since 6.8.x release).