Seitenhistorie
...
ACOnet currently recommends using one of these Free/Libre software projects, which can be integrated with most any software or website:
- Shibboleth EDS (HTML/JS- only, fully stand-alone, easiest when also using requires a set of IDPs in JSON format as produced by the Shibboleth SP software software)
- SWITCHwayf (PHP server software; its "embedded" integration method via is HTML/JS-only but 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
- Seamless Access (an external service not provided operated by ACOnet) provides several integration methods and may already be known to some/many of your service's users from other services's reliance on Seamless Access.
- Note that the button from the so-called "Standard" integration method – arguably SeamlessAccess' main achievement – never remembers will never remember selected IDPs (and therefore has a worse UX than any of the existing alternatives) when if the web browser blocks 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 IDP 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 triggertriggers the browser's the browsers privacy protection (if enabled). This integration method will therefore likely be collateral damage once more web browsers will block more kinds of "third-party" access to cookies and local storage.
- Note that the button from the so-called "Standard" integration method – arguably SeamlessAccess' main achievement – never remembers will never remember selected IDPs (and therefore has a worse UX than any of the existing alternatives) when if the web browser blocks 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 IDP 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 triggertriggers the browser's the browsers privacy protection (if enabled). This integration method will therefore likely be collateral damage once more web browsers will block more kinds of "third-party" access to cookies and local storage.
| Panel | ||
|---|---|---|
| ||
See SAML Demo SP, section "IDP Discovery Services" for descriptions of the several methods demonstrated by the eduID.at Demo SP. |
...
Überblick
Inhalte
Aufgabenbericht