I5:FeatureTest-RP Support for NonEV HTTPS

{{#vardefine:DtArticleSortKey|}}

RP Support for NonEV HTTPS

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-RP Support for NonEV HTTPS}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:RP Support for NonEV HTTPS|{{#if:{{#var:DtArticleSortKey}}||}}}}{{#ifeq:{{#var:header}}|no||

{{#ifeq:no|no||

{{#if:{{#var:refs}}|[[{{#var:page}}|no_ref's]]|[[Special:Call/DT Article show Refs,page={{#var:page}},refs=yes|ref's]]}}}}

{{#if:{{#var:DtArticleSortKey}}|({{#var:DtArticleSortKey}})}}    list help  [[Special:Call/DT Article copy,cat=FeatureTest,from={{#var:page}},namespace=I5|copy]]  [[Special:Call/DT Articles list XML,type=FeatureTest,title={{#var:page}},namespace=I5|as XML]]  edit

}}

{{#if:|Feature Test |Feature Test }}	RP Support for NonEV HTTPS
Test Type	bgcolor={{{color}}}}}|SSL Support
Identifier	bgcolor={{{color}}}}}|FTR-irp-rpssl-2
Description	bgcolor={{{color}}}}}|Tests Identity Selector & RP support for HTTP Protocol transactions
Role tested	bgcolor={{{color}}}}}|Information Card Relying Party
Known Successful Reference Solution(s)	bgcolor={{{color}}}}}|{{ #if: CardSpace .NET Framework 3.5 | I5:CardSpace .NET Framework 3.5}}{{ #if: | [[I5:]]}} {{ #if: | }} {{ #if: | }}
Success Criteria	bgcolor={{{color}}}}}|Selector is triggered and transaction succeeds
Failure Criteria	bgcolor={{{color}}}}}|Selector does not trigger or transaction does not succeed

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=I5
 |linksto=I5:FeatureTest-RP Support for NonEV HTTPS
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-RP Support for NonEV HTTPS/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

1. Open the Relying Party and trigger an information card transaction
2. Ensure that the selector is triggered
3. Use a card
4. Check that the transaction was successful
5. Update the result for your solution
   1. Set outcome:
      1. If the selector does not trigger or the transaction does not complete properly, mark the outcome as Failed
      2. If the selector triggers and the transaction succeeds, mark the outcome as Works
      3. If you saw specific issues, mark the outcome as "Issues" and outline the issues by commenting on the "Talk" tab of this page
6. Add either four tilde ~~~~ signs or a text name into the "testedby" parameter
7. Update the date tested, operating systems, and tested solutions parameters of the results page