You create managed card templates when you want the Identity Server to act as an identity provider. Users can then use the templates to create managed cards and use the cards to log into the Identity Server.
When a user uses a managed card, certain information about the managed card is stored on the user’s computer: the card name, the date that the card was installed, a “valid-through” date, and a history of the sites where this card was used.
In the Administration Console, click
> > > > .The table displays the following information about the templates you have created.
Name: A list of the managed card templates that can be modified. To modify the template, click the name.
Description: The description you have provided for the template. This is an optional configuration field, so it might be blank.
Select from the following actions:
New: To create a new managed card template, click Section 8.8.1, General Template Details.
. For configuration details, seeDelete: To delete a managed card template, select the template, then click
. To delete all templates, click the check box, then click .Click
twice, then update the Identity Server if you have modified the configuration.Use the Managed Card page to create a new template or to modify the general details of an existing template.
In the Administration Console, click
> > > > > .Configure the following fields:
Name: Specify a display name for the template.
Description: Specify the text to be displayed on the card. This can contain information about how the card can be used or the type of resource that can be accessed with the card.
Image: Specify the image to be displayed on the card. Select the image from the drop-down list. To add an image to the list, click
.Require Identification of Relying Party in Security Token: Select this option to require the relying party to provide identification when it requests a security token for the user that is using the card to establish authentication credentials.
Allow Users to Back a Managed Card Using a Personal Card: When this option is selected, the user is presented with the option to back the managed card with a personal card. When this option is not selected, the option to back the managed card with a personal card is removed from the user interface.
When a managed card is backed by a personal card, the user enters the required credentials once, and thereafter only the card is needed for authentication.
When a managed card is not backed by a personal card, the user must always enter the required credentials on authentication.
Select one of the following actions:
To configure the attributes, continue with Section 8.8.2, Template Attributes.
To save your changes, click
twice, then update the Identity Server.Use the Attribute page to select the claims that are available on the managed card.
In the Administration Console, click
> > > > > > .Configure the following fields:
Attribute set: From the list of available sets, select the default CardSpace set or the set that you have created for CardSpace claims. To create a new attribute set, select
.If the set you have created for CardSpace is not listed, you need to configure the STS to use the set. Click
> > > to manage the claims that are available.Selected claims: From the list of
, select the attributes for the managed card and move them to the list of .Click
if you are modifying a template, or click if you are creating a template.Click
, then update the Identity Server.