5
Doesn't store, doesn't communicate.
7
Modeled on liberty profiles; one profile = one class
9
Objet oriented but in C. Talks about how this work (necessary to know for the
10
lasso_profile functions)
14
Lasso provides the necessary functions to implement Liberty Alliance profiles,
15
as defined in the `Liberty ID-FF Bindings and Profiles Specification`_ and
16
explained in the previous chapter. Each profile maps to a Lasso class:
18
===================================== =============================
19
Single Sign-On and Federation LassoLogin
20
Name Registration LassoRegisterNameIdentifier
21
Federation Termination Notification LassoFederationTermination
22
Single Logout LassoLogout
23
Name Identifier Mapping LassoNameIdentifierMapping
24
Identity Provider Introduction *not implemented*
25
Name Identifier Encryption *not implemented*
26
===================================== =============================
29
There are also a few other classes to know about:
31
- LassoServer holds the data about a provider, which other providers it knows,
32
what certificates to use, etc.
34
- LassoIdentity holds the data about a Liberty federated identity
35
- LassoSession holds the data about an active Liberty session.
37
- LassoProfile is the base class for profiles.
40
Talk more about respective usage of Identity and Session.
43
.. _Liberty ID-FF Bindings and Profiles Specification:
44
http://www.projectliberty.org/specs/draft-liberty-idff-bindings-profiles-1.2-errata-v1.0.pdf
added
removed
docs/lasso-book/lasso-architecture.rst
