SourceID/PingID Rollout Expectations
Bryan Field-Elliot <[email protected]> 10 Apr 2003 14:55:31 -0600
| Newsgroups | gmane.comp.sourceid.sso.announce |
|---|---|
| Message-ID | <[email protected]> |
--=-swK2CHuhBiZ6mJ/O/Y1R
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
There are four milestones in the upcoming weeks which I wanted to keep
everyone appraised of. Much of this information was already posted here
a month or so ago, but there have been a lot of new subscribers to this
mailing list and I wanted to be sure everyone was aware of what to
expect.
In the late April/early May timeframe, SourceID and PingID intend to
deliver:
1. Version 1.0 Final of SourceID-SSO, with 100% coverage of the Liberty
Protocol 1.1 specifications.
There are a couple of minor bugs yet to fix, including timezone
handling in the timestamps produced, and automatic artifact expiration
after a certain period. In addition, support is missing for three
profiles: Identity Provider Introduction (a simpe cookie mechanism),
WML, and LECP. These final profiles (which we have estimated to be the
least popular profile sets) will be added prior to 1.0 Final release.
2. PingID Federation Manager
PingID will formally launch the PingID Federation Manager, a
self-service provisioning system to aid in the construction, deployment,
and maintenance of Liberty service trust circles between site operators.
With the PingID Federation Manager, you can manage your trust circles
and individual sites, publish or update Liberty metadata for your sites,
and subscribe to changes in other sites' metadata. This service can be
used with any Liberty Protocol implementation. However, if using
SourceID-SSO, then you'll have the added benefit of automatic
downloading and updating of trust circle metadata into your local site
metadata directory.
3. Always-on Server
PingID will host and manage an always-on server using SourceID-SSO
and a "mock" Identity Provider and Service Provider, for easy testing
and validation of Liberty deployments or implementations. Simply
register your site with the Federation Manager, join the PingID LIVE
Trust Circle, and you can begin testing immediately of your IDP, SP, or
both, against our Always-on Server.
4. RSA Conference Demo with Jabber Interoperability
Next week at the RSA Conference, Jabber and PingID will be
demonstrating joint deployment of a Liberty-enabled sample corporate
portal/401k web application. The demo show single sign-on from an
Identity Provider website (corporate portal), to a Service Provider
website (outsourced 401k provider), to a Help Desk application based
upon Jabber. Following the RSA show, we'll be publishing a short
whitepaper on how Liberty-compliant Single Sign-on with Jabber was
achieved. And if you happen to be in the San Francisco area, be sure to
drop by the RSA conference and meet the principals of PingID at the
Project Liberty booth.
Thank you,
Bryan Field-Elliot
Chief Architect, SourceID-SSO
--=-swK2CHuhBiZ6mJ/O/Y1R
Content-Type: text/html; charset=utf-8
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/1.0.4">
</HEAD>
<BODY>
There are four milestones in the upcoming weeks which I wanted to keep everyone appraised of. Much of this information was already posted here a month or so ago, but there have been a lot of new subscribers to this mailing list and I wanted to be sure everyone was aware of what to expect.
<BR>
<BR>
In the late April/early May timeframe, SourceID and PingID intend to deliver:
<BR>
<BR>
1. Version 1.0 Final of SourceID-SSO, with 100% coverage of the Liberty Protocol 1.1 specifications.
<BR>
There are a couple of minor bugs yet to fix, including timezone handling in the timestamps produced, and automatic artifact expiration after a certain period. In addition, support is missing for three profiles: Identity Provider Introduction (a simpe cookie mechanism), WML, and LECP. These final profiles (which we have estimated to be the least popular profile sets) will be added prior to 1.0 Final release.
<BR>
<BR>
2. PingID Federation Manager
<BR>
PingID will formally launch the PingID Federation Manager, a self-service provisioning system to aid in the construction, deployment, and maintenance of Liberty service trust circles between site operators. With the PingID Federation Manager, you can manage your trust circles and individual sites, publish or update Liberty metadata for your sites, and subscribe to changes in other sites' metadata. This service can be used with any Liberty Protocol implementation. However, if using SourceID-SSO, then you'll have the added benefit of automatic downloading and updating of trust circle metadata into your local site metadata directory.
<BR>
<BR>
3. Always-on Server
<BR>
PingID will host and manage an always-on server using SourceID-SSO and a "mock" Identity Provider and Service Provider, for easy testing and validation of Liberty deployments or implementations. Simply register your site with the Federation Manager, join the PingID LIVE Trust Circle, and you can begin testing immediately of your IDP, SP, or both, against our Always-on Server.
<BR>
<BR>
4. RSA Conference Demo with Jabber Interoperability
<BR>
Next week at the RSA Conference, Jabber and PingID will be demonstrating joint deployment of a Liberty-enabled sample corporate portal/401k web application. The demo show single sign-on from an Identity Provider website (corporate portal), to a Service Provider website (outsourced 401k provider), to a Help Desk application based upon Jabber. Following the RSA show, we'll be publishing a short whitepaper on how Liberty-compliant Single Sign-on with Jabber was achieved. And if you happen to be in the San Francisco area, be sure to drop by the RSA conference and meet the principals of PingID at the Project Liberty booth.
<BR>
<BR>
<BR>
Thank you,
<BR>
<BR>
Bryan Field-Elliot
<BR>
Chief Architect, SourceID-SSO
<BR>
</BODY>
</HTML>
--=-swK2CHuhBiZ6mJ/O/Y1R--