Skip to main content
Jump to: navigation, search

HBX Microsoft CardSpace Support


Higgins logo 76Wx100H.jpg

HBX supports the Microsoft-defined CardSpace web integration flow described in this paper. When the user points their browser at a website, HBX parses the HTML looking for embedded indicators of the security policy of the website, that in this case is acting as a Relying Party Agent (RPA). The security policy indicates the Digital Identity (DI) that the website desires or requires in order to authenticate or otherwise interoperate with the user.

<object> tag Support

HBX looks for the x-information-typg <object> tag, requests an appropriate Digital Identity token from the Higgins server, retreives it and posts it to the RPA.

In addition to detecting the <object> tag as before, this version also parses and captures each of the parameters (see example below) and values and passes these along to a Higgins server. This has been added in order to support work on the server related to integrating an STS for upcoming demos next week. This version also passes along the website's SSL certificate to the Higgins server.

      <OBJECT type="application/x-informationCard" name="xmlToken">
         <PARAM Name="tokenType" Value="urn:oasis:names:tc:SAML:1.0:assertion">
         <PARAM Name="issuer" Value="">
         <PARAM Name="requiredClaims" Value=",

Binary Behaviors Support

NOTE: We PLAN support for binary behaviors very soon, but as of version 0.4.8 it is NOT supported.

Microsoft's new uses the "binary behavior" option instead of the <object> tag described above. Here is a sample page:

   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
   <html xmlns="" xmlns:ic>
   <head><title>Microsoft Live Labs Relay Service: Downloads</title>
   <link xhref="App_Themes/site_styles.css" rel="stylesheet" type="text/css" />
     style='behavior: url(#default#informationCard)'
   <ic:add claimtype='' optional='false' />

Back to the top