Page History
...
- Shibboleth EDS (HTML/JS- only, fully stand-alone, easiest when also using the Shibboleth SP software)
- SWITCHwayf (PHP server software; its "embedded" integration method via HTML/JS-only still requires a full SWITCHwayf instance elsewhere, though ACOnet provides one such instance)
- The "Standard" integration method with the SeamlessAccess service (HTML/JS-only integration with an external service not provided by ACOnet)
- Note that the button from the "Standard" integration method – arguably SeamlessAccess' main achievement – never remembers selected IDPs (and therefore has a worse UX than any of the existing alternatives) when 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 doesn't do anything nefarious with its cross-site access: It merely helps your web browser to locally remember previously selected IDPs across all the services you may be using. But what some code blocked from execution would do if it were not blocked cannot factor into the browser's decision and so SeamlessAccess becomes a victim of (otherwise sensible and recommendable) privacy protection measuresonly stores your recently used IDP 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 trigger's the browsers privacy protection (if enabled).
- Note that the button from the "Standard" integration method – arguably SeamlessAccess' main achievement – never remembers selected IDPs (and therefore has a worse UX than any of the existing alternatives) when 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 doesn't do anything nefarious with its cross-site access: It merely helps your web browser to locally remember previously selected IDPs across all the services you may be using. But what some code blocked from execution would do if it were not blocked cannot factor into the browser's decision and so SeamlessAccess becomes a victim of (otherwise sensible and recommendable) privacy protection measuresonly stores your recently used IDP 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 trigger's the browsers privacy protection (if enabled).
| Panel | ||
|---|---|---|
| ||
See SAML Demo SP, section "IDP Discovery Services" for descriptions of the several methods demonstrated by the eduID.at Demo SP. |
...
| Info | ||||
|---|---|---|---|---|
| ||||
|
| Info | ||||
|---|---|---|---|---|
| ||||
|
An alternative external fallback IDP discovery service is the SeamlessAccess one, when used with their "Limited" integration method. (Though you can use their other integration methods, too, of course.)
Overview
Content Tools
Tasks