[OpenID] opensso wiki. good resource for websso engineering.

Peter Williams

2009-04-12 15:52:01 UTC

--_000_BFBC0F17A99938458360C863B716FE46398DDA3CCFsimmbox01rapn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've been finding it useful to research the SUN engineering communities "op=
ensso" initiative, particularly when it comes to thinking about "what is mi=
ssing in openid" for generalized, SSL-style "social" adoption: http://wiki=
s.sun.com/display/OpenSSOd11n/Sun+OpenSSO+Documentation.

Now, it would be nice if SUN could openid-enable that wiki, to leverage th=
eir own openid OP perhaps. Or, if openid is too difficult a marketing-step=
within SUN, perhaps just websso-enable the wiki (with SAML2 say, using the=
"dynamic metadata" model that makes SAML act very much like openid 2 disc=
overy with signed XRDSs).

Websso has been a longtime coming - and most vendors have reduced their pit=
ch to address only the basic functions (posted assertion making and then re=
liance). Now that many of us of doing the basic functions... and hitting th=
e limits of the simple profiles, I suspect it time to rollout out all the a=
dvanced stuff again!

--_000_BFBC0F17A99938458360C863B716FE46398DDA3CCFsimmbox01rapn_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln=
s:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D=
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"http://sc=
hemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.micro=
soft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2000/09/=
xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" xmlns:u=
dc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org=
/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/=
2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"=
http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.micro=
soft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-in=
stance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udc=
xf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http:/=
/schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.micr=
osoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft=
.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/o=
ffice/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/package=
/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats.org/ma=
rkup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/200=
4/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/re=
lationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" xm=
lns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types" xml=
ns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messages" x=
mlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" x=
mlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Publis=
hedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"" x=
mlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>I’ve been finding it useful to research the SUN =
engineering
communities “opensso” initiative, particularly when it comes to=
thinking
about “what is missing in openid” for generalized, SSL-style &#=
8220;social”
adoption:  <a
href=3D"http://wikis.sun.com/display/OpenSSOd11n/Sun+OpenSSO+Documentation"=

http://wikis.sun.com/display/OpenSSOd11n/Sun+OpenSSO+Documentation</a>.<o:=

p></o:p></p>

<p class=3DMsoNormal><o:p> </o:p></p>

<p class=3DMsoNormal>Now, it would be nice if SUN could  openid-enable=
that
wiki, to leverage their own openid OP perhaps. Or, if openid is too difficu=
lt  a
marketing-step within SUN, perhaps just websso-enable the wiki (with SAML2 =
say,
using the “dynamic metadata”  model that makes SAML act ve=
ry much
like openid 2 discovery with signed XRDSs). <o:p></o:p></p>

<p class=3DMsoNormal><o:p> </o:p></p>

<p class=3DMsoNormal>Websso has been a longtime coming – and most ven=
dors
have reduced their pitch to address only the basic functions (posted assert=
ion making
and then reliance). Now that many of us of doing the basic functions…=
and
hitting the limits of the simple profiles, I suspect it time to rollout out=
all
the advanced stuff again!<o:p></o:p></p>

</div>

</body>

</html>

--_000_BFBC0F17A99938458360C863B716FE46398DDA3CCFsimmbox01rapn_--