Difference between revisions of "OC5:FeatureTest-Can Provide Signed UserInfo Response"

From OSIS Open Source Identity Systems
Jump to: navigation, search
m (1 revision: Cloning for OC5 Interop)
(Specify default algorithms)
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
 
   |areatested        =  
 
   |areatested        =  
 
   |status            = active
 
   |status            = active
   |summary            = Accept registration for signed UserInfo responses and send them
+
   |summary            = Accept registration for signed UserInfo responses using RS256 and send them
 
   |testedrole        = OP
 
   |testedrole        = OP
 
   |referencesolution1 =  
 
   |referencesolution1 =  

Latest revision as of 17:35, 11 June 2014

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Can Provide Signed UserInfo Response}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Can Provide Signed UserInfo Response|{{#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=OC5|copy]]  [[Special:Call/DT Articles list XML,type=FeatureTest,title={{#var:page}},namespace=OC5|as XML]]  edit
}}
{{#if:|Feature Test |Feature Test }}   Can Provide Signed UserInfo Response
Test Type   bgcolor={{{color}}}}}|normal
Identifier   bgcolor={{{color}}}}}|FTR-op-ui-sign  
Description   bgcolor={{{color}}}}}|Accept registration for signed UserInfo responses using RS256 and send them  
Role tested   bgcolor={{{color}}}}}|OP  
Known Successful Reference Solution(s)   bgcolor={{{color}}}}}|{{ #if: |
[[OC5:]]}}{{ #if: |
[[OC5:]]}} {{ #if: |
}} {{ #if: |
}}  
Success Criteria   bgcolor={{{color}}}}}|Accepts registration for signed UserInfo responses and sends them  
Failure Criteria   bgcolor={{{color}}}}}|Registration not accepted or UserInfo response not signed  

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=OC5
 |linksto=OC5:FeatureTest-Can Provide Signed UserInfo Response
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Can Provide Signed UserInfo Response/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

  1. Run the automated OP testing tools either using the online OP test site at http://openidtest.uninett.no/test#!/connect or by downloading and running the OP testing scripts at http://www.kodtest.se/oictest/.
    1. Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
  2. Open the result page for your solution and this test.
  3. Record the outcome from the test "(mj-60)RP wants signed UserInfo returned" in the results page:
    1. If the success criteria was met, set the outcome to "Works".
    2. If the test failed, set the outcome to "Failed" and enter information about the failure in the Notes section.
    3. If other issues occurred set the result to "Issues" and describe them in the Notes section.
  4. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
  5. Update the Date Tested, Browser, and Operating System lines of the results page.