Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

ISIP Interop Issues

{{#eclipseproject:technology.higgins}}

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

Li Tie for the RCP selector perspective:

  1. We need a better understand of the IE 7's informationCard default behavior (for our HBX-IE).
  2. It's better for Microsoft to create some API in IE, to integrate with other card selectors like Higgins.

.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 just refuse to load card collection. But we able to import this card, if IssuerId contains an accidental base64-encoded value. Only information we found out in the CardSpace thechref about IssuerId is the following: "This required element contains an identifier for the identity provider using which a selfissued 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.
    • Why this value is required to import a managed card with not self-issued credentials.
    • What algorithm should we use to calculate this value.

Back to the top