Difference between revisions of "ISIP Interop Issues"

Revision as of 12:40, 21 May 2008

{{#eclipseproject:technology.higgins}}

Things we would like Microsoft to change about CardSpace (UI, selector, RP functionality,etc.)

Browser/Selector Integration:

1. We need a better understand of the IE 7's informationCard default behavior (for our HBX-IE).

.CRD File Format:

1. Right now we have some troubles with import of managed cards with username/password credentials from higgins into CardSpace (using .crds file format). It looks like the problem is related to the value of IssuerId element (<ic:RoamingInformationCard>/<ic:InformationCardMetaData>/<ic:IssuerId>) which is practically not documented in the latest CardSpace tech references we're able to find. If IssuerId element in our roaming card is missing or contains no value CardSpace refuses to load card collection. On the other hand CardSpace will import this card, if IssuerId contains a random base64-encoded value. The CardSpace tech refs about IssuerId says the following: "This required element contains an identifier for the identity provider using which a self-issued credential descriptor in a card issued by that identity provider can be resolved to the correct self-issued card. The element content may be empty." So, there are the following questions:
   • How exactly CardSpace uses IssuerId value?
   • What algorithm should we use to calculate this value.
   • --Paul.socialphysics.org 12:17, 21 May 2008 (EDT): Mike M says that according to schema it is required
   • --Paul.socialphysics.org 12:21, 21 May 2008 (EDT): MikeM asks: if two cards have the same issuer (URI) should they have the same issuerId?

.CRD Format Extensibility

1. We would like to be able to specify protocol(s) (instead of being WS-Trust-only)
2. Need to clarify that "extra" XML elements are:
   • ignored on import
   • preserved and exported
3. We need to confirm that extra spaces are now tolerated
4. May need PIN protection on some of the new extensibility elements

.CRDS Format

1. We would like the export format to include card history
2. We need a way to efficiently associate a managed card with the personal card that is backing it
3. May need PIN protection on some of the new extensibility elements. E.g. Protecting Cached intermediate values required to compute PPID RP-Id vales. (Perhaps {scheme,host,port} <--> digests of CA chain)