Re: Advice on Liberty Protocol Reading

Hi Steven,

The short way to think about what the Liberty Protocol offers is this:

1. Single sign-on across sites, with each site in either the "consumer"
role ("Service Provider"), or "authenticator" role ("Identity
Provider").
2. End-users can link, or unlink, their accounts across sites, so they
can benefit from Single sign-on.
3. Global Logout, where every site can have a "logout" button which logs
the user out of all sites they've authenticated against.

In version 2.0 of Liberty (and SourceID), you'll be able to build
Identity Web Services, which basically allow rich exchange of identity
attribute information along the lines you describe. It requires as a
foundation the services described above (Liberty 1.x).

The drafts of the Liberty 2.0 protocol are a bit dense, it's hard to get
a birdseye view from reading them. Try this one for starters:

http://projectliberty.org/specs/draft-lib-arch-idwsf-primer-v1.0-04.pdf

Thanks and regards,


________________________________________________________________________
Bryan Field-Elliot
CTO, Ping Identity Corporation
Federated Identity Management Solutions
Info: http://pingidentity.com
Email: [email protected]



On Mon, 2003-08-04 at 06:11, [email protected] wrote:

> Hi All. I have been looking round the Liberty site and was a little overwhelmed by the amount of doco to read (on top of a number of other things i have on the go at the moment).
> 
> My key interest is in integrating authentication within my own site using Liberty, with a view of a circle of trust type authentication on a set of distributed sites I am creating. Useage of secure shared profile information is something i am also looking at in the future.
> 
> The type of shared attributes is quite specific (e.g. financial preferences) so I will want to think about how to easily and securely share this information amoungst a closed set of sites.
> 
> I'm appreciated pointers to the parts of the Liberty specs I should read to get this information with a view to integrating the current .Net software (which i believe is derived from the SourceID.Java vesion) into my framework.
> 
> Best Wishes,
> Steven.
> _______________________________________________
> sso-dev mailing list
> [email protected]
> http://mail.sourceid.org/mailman/listinfo/sso-dev