Defining Use Cases for Federating Library Services

["Dale,Andy" <>]

Diagram 1 shows the basic decision tree that takes place in a typical
EZProzy configuration using Shibboleth for authentication. The primary
success path is highlighted in red and is explored in detail in diagrams
2, 3 and 4. Note that the colors and the 'sync points' (numbered stars)
are used consistently across this set of diagrams to let you 'map' the
flows onto each other.

Diagrams 2, 3 and 4 all depict versions of the primary success flow from
diagram 1. They differ in the details of the authentication mechanics:
Diagram 2 shows an initial login that includes user interaction. Diagram
3 shows a login at EZProxy that is 'silent' for the user as they have
previously established a session at the campus IDP, presumably by
logging in to a different web site. Diagram 3 shows a request to EZProxy
after the user has already authenticated to the EZProxy previously
(recently enough that their 'session' is still valid). 

Diagram 5 depicts a protected Abstracts site and a campus OpenURL Link
Resolver to show an example where the primary success flow is entered
twice but the authentication mechanism that is followed is different
each time.

Attachment: 5) starting with a OpenURL.png
Description: 5) starting with a OpenURL.png

Attachment: 4) IPAuth Access via EXProxy with Session.png
Description: 4) IPAuth Access via EXProxy with Session.png

Attachment: 3) IPAuth Access via EXProxy and Shib SSO.png
Description: 3) IPAuth Access via EXProxy and Shib SSO.png

Attachment: 2) IPAuth Access via EXProxy and Shib.png
Description: 2) IPAuth Access via EXProxy and Shib.png

Attachment: 1) Basic EZProxy Access Flow.png
Description: 1) Basic EZProxy Access Flow.png