CINXE.COM
Blog - SeamlessAccess
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="x-ua-compatible" content="ie=edge"> <title>Blog - SeamlessAccess</title> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="icon" href="https://seamlessaccess.org/favicon.png"> <link rel="stylesheet" href="/css/style.min.a7afcb5eb59fa2b4c18e7985ffc8c11fc0264d5d4c71689658096ea610ca2e1c.css"> </head> <body class='page page-posts-single'> <div id="main-menu-mobile" class="main-menu-mobile"> <ul> <li class="menu-item-the service"> <a href="/services/"> <span>The Service</span> </a> </li> <li class="menu-item-stakeholders"> <a href="/stakeholders/"> <span>Stakeholders</span> </a> </li> <li class="menu-item-documentation"> <a href="https://seamlessaccess.atlassian.net/wiki/spaces/DOCUMENTAT/overview"> <span>Documentation</span> </a> </li> <li class="menu-item-learning center"> <a href="/learning-center/"> <span>Learning Center</span> </a> </li> <li class="menu-item-about"> <a href="/about/"> <span>About</span> </a> </li> <li class="menu-item-blog active"> <a href="/posts/"> <span>Blog</span> </a> </li> </ul> </div> <div id="wrapper" class="wrapper"> <div class='header header-absolute'> <div class="container"> <div class="logo"> <a href="https://seamlessaccess.org/"><img alt="SeamlessAccess Homepage" src="https://seamlessaccess.org/images/logo.svg" /></a> </div> <div class="logo-mobile"> <a href="https://seamlessaccess.org/"><img alt="SeamlessAccess Homepage" src="https://seamlessaccess.org/images/logo-mobile.svg" /></a> </div> <div id="main-menu" class="main-menu"> <ul> <li class="menu-item-the service"> <a href="/services/"> <span>The Service</span> </a> </li> <li class="menu-item-stakeholders"> <a href="/stakeholders/"> <span>Stakeholders</span> </a> </li> <li class="menu-item-documentation"> <a href="https://seamlessaccess.atlassian.net/wiki/spaces/DOCUMENTAT/overview"> <span>Documentation</span> </a> </li> <li class="menu-item-learning center"> <a href="/learning-center/"> <span>Learning Center</span> </a> </li> <li class="menu-item-about"> <a href="/about/"> <span>About</span> </a> </li> <li class="menu-item-blog active"> <a href="/posts/"> <span>Blog</span> </a> </li> </ul> </div> <button id="toggle-main-menu-mobile" class="hamburger hamburger--slider" type="button"> <span class="hamburger-box"> <span class="hamburger-inner"></span> </span> </button> </div> </div> <div id="hero" class="hero-image hero-image-setheight" style="background-image: url('/images/hero_news.jpg')"> <div class="container"> <div class="row"> <div class="col my-auto"> <div class="sa-text"> <h1>News</h1> <p><strong></strong>Learn the latest about SeamlessAccess</p> </div> </div> </div> </div> </div> </div> <div class="intro intro-big pt-2 pt-md-4 pb-2 pb-md-2"> <div class="container"> <div class="row"> <div class="col-12"> </div> </div> </div> </div> <div class="container pb-6"> <div class="row"> <div class="col-12 col-md-8"> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2024-10-16-storage-access-api/">A new chapter in the ‘browser changes’ journey: Preparing for the switch to Storage Access API</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Oct 16, 2024</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>A new chapter in the ‘browser changes’ journey: Preparing for the switch to Storage Access API Over the last couple of years, we have posted regularly about changes that are being made to the way that browsers work and how those changes will affect SeamlessAccess (see e.g. this post from Feb 2024 or this post from Nov 2023 and references therein). These changes primarily impact SeamlessAccess’ ability to remember the user’s choice of home institute across participating websites, a functionality that we refer to as “global persistence”.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2024-10-16-storage-access-api/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2024-09-03-deprecation-trial-phase2/">Signed up for Storage Partitioning trial? Time to renew!</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Sep 3, 2024</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Signed up for Google’s storage partitioning trial? Time to renew! As we talked about in a post back in February “Calling all SeamlessAccess integrators to participate in deprecation trial for unpartitioned third-party storage” - and before that as part of a longer explanation back in 2023 - the team that works on Google Chrome has made available a limited-time trial that allows participating sites to continue to use unpartitioned storage in the browser.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2024-09-03-deprecation-trial-phase2/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2024-08-14-google-3ppcookies-announcement/">Google’s updated approach to third-party cookies: What does it mean for SeamlessAccess?</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Aug 14, 2024</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Google’s updated approach to third-party cookies: What does it mean for SeamlessAccess? In a blog post that came out in April, we spoke about changes to browser technology and what impact those are likely to have on access experiences and SeamlessAccess. At the time, following Google’s communication on the subject, we worked under the understanding that Google would roll out deprecation of third-party cookies in Chrome to 100% by the end of this year.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2024-08-14-google-3ppcookies-announcement/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2024-04-02-important-update/">Important update for all SeamlessAccess integrators regarding the impact of browser changes.</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Apr 2, 2024</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Important update for all SeamlessAccess integrators regarding the impact of browser changes. Today’s post updates the evolving story about changes to browser engines and how those changes affect SeamlessAccess. Perhaps the most visible change in this context is the deprecation of third-party cookies by Google Chrome, which has already been rolled out to 1% of users and that will be ramped up “to reach 100% of Chrome clients by the end of Q4, subject to addressing any remaining concerns of the CMA.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2024-04-02-important-update/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2024-02-29-third-party-storage-deprecation-trial/">Calling all SeamlessAccess integrators to participate in deprecation trial for unpartitioned third-party storage</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Feb 29, 2024</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Calling all SeamlessAccess integrators to participate in deprecation trial for unpartitioned third-party storage In a blog post published towards the end of last year, we spoke about an update to Google’s Chrome browser that by default enabled a new feature called Storage Partitioning. This feature effectively blocks third-party websites from accessing information held in the local browser storage, which is used by SeamlessAccess to show the user’s remembered choice of institute in its button.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2024-02-29-third-party-storage-deprecation-trial/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2023-11-16-3pp-cookies-and-the-sa-button/">Third-party cookie deprecation and its effect on SeamlessAccess</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Nov 15, 2023</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Third-party cookie deprecation and its effect on SeamlessAccess Is your SeamlessAccess button acting weird? Not showing your remembered institute as you expect? This might be due to a new browser configuration setting that blocks third-party cookies. Without those cookies, the SeamlessAccess button (i.e. “Access through..”) will work differently than you might expect - but the other SeamlessAccess services (login, discovery, remembered choice on the discovery page) continue to work as before.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2023-11-16-3pp-cookies-and-the-sa-button/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2023-07-07-fedcm-update/">FedCM: July Update</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Jul 7, 2023</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>FedCM: July update on the efforts between the R&E community, the web community, and browser vendors This is an update following continuous meet-ups and other gatherings between representatives of the Research & Education (R&E) community and the browser vendors – discussing what capabilities in and around FedCM are required for our community to continue to serve academic users and their use cases. Background In a blog post titled “An emerging new technology for federated access: Federated Credential Management (FedCM)” and several later blog posts (most recent, previous), videos (one, two) and FAQs (for librarians and publishers), we discussed ongoing developments at the major browser vendors that are bound to have a significant impact on how users will experience the web in general, and on federated access in particular.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2023-07-07-fedcm-update/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2023-03-20-fedcm-postevent/">FedCM: Update</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Mar 20, 2023</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>FedCM: An update on the efforts between the R&E community and browser vendors This is an update following a recent meet-up between representatives of the Research & Education (R&E) community and Mozilla and Google – discussing what capabilities in and around FedCM are required for our community to continue to serve academic users and their use cases. Note: SeamlessAccess is organizing a more in-depth webinar on this topic on April 6 - register here!</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2023-03-20-fedcm-postevent/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2023-02-20-fedcm/">Federated Credential Management (FedCM)</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Feb 20, 2023</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>An emerging new technology for federated access: Federated Credential Management (FedCM) In earlier blog posts, videos (one, two) and FAQs (for librarians and publishers), we talked about ongoing developments at the major browser vendors that are bound to have a significant impact on how users will experience the web in general, and on federated access in particular. To recap, these changes are driven by concerns around user privacy - including regulations such as GDPR - and meant to stop the unsanctioned tracking of users across the web.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2023-02-20-fedcm/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> <div class="post post-summary mb-4"> <div class="post-title"> <h2><a href="/posts/2022-10-31-contractlanguagemodellicense/">Contract Language Model License Agreement 1.0</a></h2> </div> <div class="post-meta"> <div class="post-date"> <span class="post-date-date">Oct 31, 2022</span> </div> </div> <div class="post-description"><p></p></div> <div class="post-content"> <p>Contract Language Model License Agreement 1.0 The Contract Language Working Group is pleased to release the Federated Authentication Contract Language Model License Agreement 1.0. From the introduction: “Existing contract language between resource providers and libraries is almost universally focused on authentication and authorization via IP address. Reference to federated access is most often with language that refers to “secure networks”, and the authorization of users that are on said network to access resources.</p> </div> <div class="post-categories"> <strong>Categories:</strong> <a class="post-category" href="/categories/general">General</a> </div> <div class="post-link"><a class="post-read-more" href="https://seamlessaccess.org/posts/2022-10-31-contractlanguagemodellicense/" >Read More<i class="fas fa-long-arrow-alt-right ml-1"></i></a></div> </div> </div> <div class="col-12 col-md-4"> <div class="sidebar"> <h3>Recent News</h3> <ul> <li> <a href="/posts/2024-10-16-storage-access-api/">A new chapter in the ‘browser changes’ journey: Preparing for the switch to Storage Access API</a> </li> <hr> <li> <a href="/posts/2024-09-03-deprecation-trial-phase2/">Signed up for Storage Partitioning trial? Time to renew!</a> </li> <hr> <li> <a href="/posts/2024-08-14-google-3ppcookies-announcement/">Google’s updated approach to third-party cookies: What does it mean for SeamlessAccess?</a> </li> <hr> <li> <a href="/posts/2024-04-02-important-update/">Important update for all SeamlessAccess integrators regarding the impact of browser changes.</a> </li> <hr> <li> <a href="/posts/2024-02-29-third-party-storage-deprecation-trial/">Calling all SeamlessAccess integrators to participate in deprecation trial for unpartitioned third-party storage</a> </li> <hr> </ul> <h4>categories</h4> <ul> <li><a href="/categories/general">general</a></li> </ul> </div> </div> </div> <div class="row"> <div class="col-12"> <ul class="pagination"> <li class="pagination-item pagination-item-current"> <a href="/posts/" class="pagination-link"> 1 </a> </li> <li class="pagination-item"> <a href="/posts/page/2/" class="pagination-link"> 2 </a> </li> <li class="pagination-item"> <a href="/posts/page/3/" class="pagination-link"> 3 </a> </li> <li class="pagination-item"> <a href="/posts/page/4/" class="pagination-link"> 4 </a> </li> <li class="pagination-item"> <a href="/posts/page/5/" class="pagination-link"> 5 </a> </li> <li class="pagination-item pagination-item-next"> <a href="/posts/page/2/" class="pagination-link pagination-link-next"> » </a> </li> <li class="pagination-item pagination-item-last"> <a class="pagination-link pagination-link-last" href="/posts/page/5/"> »» </a> </li> </ul> </div> </div> </div> </div> <footer class="main-footer pr-5 pl-5 pt-3 pb-2"> <div class="container"> <div class="row"> <div class="col-12"> <div class="row"> <div class="col-12 col-md-3 col-lg-3 text-center text-xl-left text-lg-left text-md-left"> <img class="footer-logo pb-3" alt="SeamlessAcces Logo" src="/images/sa-logo-white.svg"/> <br/> <p> SeamlessAccess enables true Sign On. Your users will be able to sign in using their preferred sign in credentials, and will not be bothered for them again for all SeamlessAccess-enabled sites. </p> </div> <div class="col-12 col-md-3 col-lg-3 d-none d-xl-block d-lg-block d-md-block"> <h3 class="pr-3 pl-3 font-weight-bold lh-title primary border-left-white pt-1 pb-1 mb-0"> <a href="https://seamlessaccess.org/services/" class="link"><strong>The Service</strong></a> </h3> <ul class="pr-3 pl-3 mb-1 border-left-white"> <li><a href="https://seamlessaccess.org/stakeholders/for-service-providers/" class="link">SeamlessAccess for Service Providers</a></li> <li><a href="https://seamlessaccess.org/stakeholders/for-libraries/" class="link">SeamlessAccess for Libraries</a></li> <li><a href="https://seamlessaccess.org/stakeholders/for-identity-providers/" class="link">SeamlessAccess for Identity Providers</a></li> <li><a href="https://seamlessaccess.org/stakeholders/for-federations/" class="link">SeamlessAccess for R&E Federation Operators</a></li> <li><a href="https://seamlessaccess.org/stakeholders/for-researchers/" class="link">SeamlessAccess for Researchers</a></li> <li><a href="https://seamlessaccess.org/stakeholders/for-research_collab" class="link">SeamlessAccess for Research Collaborations</a></li> </ul> </div> <div class="col-12 col-md-3 col-lg-3 d-none d-xl-block d-lg-block d-md-block"> <h3 class="pr-3 pl-3 font-weight-bold lh-title primary border-left-white pt-1 pb-1 mb-0"> <a href="https://seamlessaccess.org/about/" class="link"><strong>About</strong></a> </h3> <ul class="pr-3 pl-3 mb-1 border-left-white"> <li><a href="https://seamlessaccess.org/about/governance/" class="link">Governance and Funding</a></li> <li><a href="https://seamlessaccess.org/about/community/" class="link">Community</a></li> <li><a href="https://seamlessaccess.org/about/trust/" class="link">Privacy and Trust</a></li> <li><a href="https://seamlessaccess.org/about/vacancies/" class="link">Vacancies</a></li> <li><a href="https://seamlessaccess.org/posts/" class="link">News</a></li> </ul> <br> <h3 class="pr-3 pl-3 font-weight-bold lh-title primary border-left-white pt-1 pb-1 mb-0"> <a href="https://seamlessaccess.org/about/" class="link"><strong>FAQ</strong></a> </h3> <br> <h3 class="pr-3 pl-3 font-weight-bold lh-title primary border-left-white pt-1 pb-1 mb-0"> <a href="https://seamlessaccess.org/work/" class="link"><strong>Documentation</strong></a> </h3> </div> </div> </div> </div> </div> </footer> <style> a:focus { box-shadow: none; outline: none } .main-footer { font-size: 14px; background: #216E93; color: white; } .main-footer a, .main-footer p { font-size: 14px; font-weight: 300; color: white; } .main-footer .primary, .main-footer a.primary { color: white; font-size: 14px; text-transform: uppercase; margin-bottom: 0; } .footer-logo { max-width: 100px; } .main-footer .link { font-size: 14px; line-height: 0; } .main-footer li { padding: 4px 0; } .sub-footer { font-size: 14px; background: #2E2E2E; color: white; } .sub-footer p { text-align: center; } .sub-footer a { font-size: 14px; text-decoration: none; } .border-left-white { border-left: none; } @media screen and (min-width: 50em) { .border-left-white { border-left: 1px solid rgba(229, 229, 229, 0.4); } .sub-footer p { text-align: left; } } </style> <div class="sub-footer pt-1 pb-1"> <div class="container"> <div class="row"> <div class="col-12 col-xl-6 col-lg-6 col-md-6 pt-1 pb-1"> <p class="mt-0 mb-0 text-center text-xl-left text-lg-left text-md-left">© 2020 All Rights Reserved <strong>SeamlessAccess</strong></p> </div> <div class="col-12 col-xl-6 col-lg-6 col-md-6 pt-1 pb-1"> <p class="mt-0 mb-0 text-center text-xl-right text-lg-right text-md-right"> <span> <a class="text-white" href="/contact"><strong>CONTACT</strong></a> </span> <span class="ml-2"><a href="https://twitter.com/seamlessaccess" target="_blank"><i class="fab fa-twitter-square text-white"></i></a></span> <span class="ml-2"><a href="https://www.youtube.com/watch?v=4xRqdc0DeJI" target="_blank"><i class="fab fa-youtube-square text-white"></i></a></span> </p> </div> </div> </div> <style> .sub-footer a, .sub-footer p { font-size: 14px; font-weight: 300; color: white; } </style> <script type="text/javascript" src="/js/scripts.min.bf1e1f7ae8e03db5f012356e825843facdff51c0a559cb0d27fe2bbe1db405c2.js"></script> </body> </html>