Page History

...

• Shibboleth EDS (HTML/JS- only, fully stand-alone, requires a set of IDPs in JSON format as produced by the Shibboleth SP software)
• SWITCHwayf (PHP server software; its "embedded" integration method is HTML/JS-only but still requires a full SWITCHwayf instance elsewhere, though ACOnet provides one such instance)
• Seamless Access (an external service not operated by ACOnet) provides several integration methods ("flavors") and may already be known to some/many of your service's users from other services' reliance on Seamless Access.
  
  • Note that the button from the so-called "Standard" integration method will never remember selected IDPs (and therefore has a worse UX than any of the alternatives) if the web browser blocks third-party cookies (as all browsers should, to protect their users' privacy from pervasive web surveillance). That's a bit unfortunate since SeamlessAccess only stores your recently used IDPs in your web browser's local storage. But it's the attempted access to those locally remembered IDP selections from multiple web sites (i.e., the web sites embedding the SeamlessAccess button/code) that requires cross-site access to your local storage and therefore triggers the browser's privacy protection (if enabled). This integration method will therefore likely be collateral damage once more web browsers will block more kinds of cross-site access to cookies and local storage.
  • This The issue mentioned above is being dealt with in the FedCM space. Until then actively being worked on. And until then it only takes a single click on the "Access through your institution" button will to take the subject to the Seamless Access service site where previously used IDPs are presented and login (and can be added/removed) and logging in to an IDP can be initiated with another single click. So at least in this case the UX "fallout" seems rather limited.

...