Date: Thu, 28 Mar 2024 20:03:44 +0000 (UTC) Message-ID: <537930438.1.1711656224359@2a96fe671a5e> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1911294566.1711656224340" ------=_Part_0_1911294566.1711656224340 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
SeamlessAccess.org supports a streamlined federated authenticati= on experience when using scholarly collaboration tools, information resourc= es, and shared research infrastructure through one=E2=80=99s home instituti= on while maintaining an environment that protects personal data and privacy= . The service aims to enable simple, trusted use of scholarly resources and= services anytime, anywhere, and on any device.
SeamlessAccess is built around a SAML federation model. SeamlessAccess i= s not, itself, a federation, but is intended for organizations that are mem= bers of a federation to make the federated authentication workflow easier f= or their users.
This page outlines the process for those who would like to implement Sea= mlessAccess.
Who does this work? For service providers ready to impl= ement SeamlessAccess for your online services, this information will be gat= hered from several different people, such as your web developer, your busin= ess developer, and/or whoever supports identity management for your service= s. During this phase of the work, you will be working closely with the Seam= lessAccess team who will help you interpret the information you have gather= ed and what it means to your organization. Based on this information, we wi= ll also be able to estimate time and resource requirements to make your sit= e SeamlessAccess enabled.
If you are a librarian, you may need to know more information on if or h= ow your institution is using federated authentication! So, your task will b= e in determining who in your organization to ask. Often those who handle sy= stem security compliance will know, as will those who manage the access con= trol to the resources that are secured by a sign-inprocess.
Lets you use the SeamlessAccess discovery service for users to find and = sign into their preferred Identity Provider, but doesn=E2=80=99t integrate = this service into your site.
Lets you use the SeamlessAccess service to display the button on your si= te, and use the SeamlessAccess discovery and persistence services as integr= ated components on your site.
Provides you with the SeamlessAccess persistence service while giving yo= u greater control over the appearance of the service on your site, and what= Identity Providers (IdPs) you include in your discovery service.
For Advanced Integrators: Contact us for a design review= .
Register and Agree to the Terms = of Service
Become a participating service
Who does this work? For the service provider, this work= is likely done by your communication or marketing team. It=E2=80=99s a gre= at idea to get this group involved early in the project so they are ready t= o talk about the connection when it is ready to launch!
If you are a librarian, you may want to develop your own plan to inform = users as to what they might expect to see as you shift your publisher agree= ments to support federated identity.
You=E2=80=99ve done the work, so we=E2=80=99d love to hear about how it= =E2=80=99s going and how you found your experience. Contact us<= /a>!
= << https://seamle= ssaccess.atlassian.net/wiki/spaces/DOCUMENTAT | User Exp= erience Scenarios >>