RE: IDFF 1.2 with several SP
"Reitzel, Charles" <[email protected]> Tue, 8 Feb 2005 10:47:01 -0500
| Newsgroups | gmane.comp.sourceid.sso.user |
|---|---|
| Message-ID | <556406FA2C8ED24281BF5EFAE9BFD6CE0225F8EE@MSGBOSCLB2WIN.DMN1.FMR.COM> |
This is a multi-part message in MIME format. --===============1561660118== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C50DF5.6E54B5E0" This is a multi-part message in MIME format. ------_=_NextPart_001_01C50DF5.6E54B5E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Javi, =20 In the <RegisterNameIdentifierRequest> element, each NameID child element has a NameQualifier attribute. Typically, this value is the SP Provider ID. You should be able to use this value to instantiate an appropriate "sub-handler" to handle the details according to the SP rules. =20 See liberty-idff-protocols-schema-v1.2.pdf, section 3.3 Name Registration Protocol =20 hth, Charlie Reitzel -----Original Message----- From: Garzon Maldonado, Jesus Javier [mailto:[email protected]]=20 Sent: Tuesday, February 08, 2005 9:58 AM To: [email protected] Subject: [SourceID SSO-users] IDFF 1.2 with several SP =09 =09 Hello all, =20 I'm trying to deploy ID-FF 1.2 in my own environment, composed of an Identity provider and several service providers. Each service provider is located in the same context, but has its own identification mechanism. =20 The demo application that comes with ID-FF only uses one idp and one sp. In sourceid-core-config.xml you can define only one AuthnAdapter and one EventAdapter for all service providers. e.g, if you have two service providers (lets say SP1 and SP2), with two different authentication mechanisms, when ID-FF 1.2 framework calls EventAdapter.onFederationCreated method, there is no way to know if principalID belongs to SP1 or SP2. =20 How can I modify demo example in order to allow more than one SP? =20 Thank you very much. =20 Best regards. =20 Javi Garzon. =20 ------_=_NextPart_001_01C50DF5.6E54B5E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML dir=3Dltr><HEAD><TITLE>Message</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD> <BODY> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2>Hi=20 Javi,</FONT></SPAN></DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2>In the=20 <FONT face=3DCourier size=3D1><RegisterNameIdentifierRequest><FONT = face=3DArial=20 size=3D2> element, each NameID child element has a NameQualifier = attribute. =20 Typically, this value is the SP Provider ID. You should be able to = use=20 this value to instantiate an appropriate "sub-handler" to handle the = details=20 according to the SP rules.</FONT></FONT></FONT></SPAN></DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2>See=20 liberty-idff-protocols-schema-v1.2.pdf, section 3.3 <EM>Name = Registration=20 Protocol</EM></FONT></SPAN></DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2>hth,</FONT></SPAN></DIV> <DIV><SPAN class=3D728584115-08022005><FONT face=3DArial color=3D#0000ff = size=3D2>Charlie Reitzel</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT=20 face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> = Garzon=20 Maldonado, Jesus Javier [mailto:[email protected]] <BR><B>Sent:</B> = Tuesday,=20 February 08, 2005 9:58 AM<BR><B>To:</B>=20 [email protected]<BR><B>Subject:</B> [SourceID SSO-users] IDFF = 1.2 with=20 several SP<BR><BR></FONT></DIV> <DIV><FONT face=3DArial color=3D#000000 size=3D2>Hello = all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I'm trying to deploy ID-FF 1.2 in my = own=20 environment, composed of an Identity provider and several service = providers.=20 Each service provider is located in the same context, but has its = own=20 identification mechanism.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The demo application that comes with = ID-FF only=20 uses one idp and one sp. In sourceid-core-config.xml you = can =20 define only one AuthnAdapter and one EventAdapter for all service = providers. e.g, if you have two service providers (lets say SP1 = and SP2),=20 with two different authentication mechanisms, when ID-FF 1.2 framework = calls=20 EventAdapter.<FONT size=3D2>onFederationCreated method, there is no = way to know=20 if principalID belongs to SP1 or SP2.</FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>How can I modify demo example in = order to allow=20 more than one SP?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thank you very much.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Best regards.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Javi Garzon.</FONT></DIV> <DIV><FONT face=3DArial = size=3D2></FONT> </DIV></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C50DF5.6E54B5E0-- --===============1561660118== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sso-users mailing list [email protected] http://lists.sourceid.org/mailman/listinfo/sso-users --===============1561660118==--