Difference between revisions of "OC5:FeatureTest-Supports Combining Claims Requested with scope and claims Request Parameter"

From OSIS Open Source Identity Systems
Jump to: navigation, search
m (1 revision: Cloning for OC5 Interop)
m (1 revision: Cloning for OC5 Interop)
Line 12: Line 12:
 
   |failure    Not all of the claims requested are returned        =  
 
   |failure    Not all of the claims requested are returned        =  
 
}}
 
}}
# Run the automated OP testing tools either using the online OP test site at http://openidtest.uninett.no/connect-provider or by downloading and running the OP testing scripts at http://www.kodtest.se/oictest/.
+
# 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/.
 
## Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
 
## Instructions on getting started with OP testing can be found at http://openidtest.uninett.no/connect-gettingstarted.
 
# Open the result page for your solution and this test.
 
# Open the result page for your solution and this test.

Revision as of 05:54, 27 June 2013

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Supports Combining Claims Requested with scope and claims Request Parameter}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Supports Combining Claims Requested with scope and Request Object|{{#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 }}   Supports Combining Claims Requested with scope and Request Object
Test Type   bgcolor={{{color}}}}}|normal
Identifier   bgcolor={{{color}}}}}|FTR-op-clm-combined  
Description   bgcolor={{{color}}}}}|Request uses email scope to request email and email_verified claims and request object to request given_name and family_name claims from UserInfo endpoint  
Role tested   bgcolor={{{color}}}}}|OP  
Known Successful Reference Solution(s)   bgcolor={{{color}}}}}|{{ #if: |
[[OC5:]]}}{{ #if: |
[[OC5:]]}} {{ #if: |
}} {{ #if: |
}}  
Success Criteria   bgcolor={{{color}}}}}|The claims email, email_verified, given_name, and family_name are all returned from the UserInfo endpoint  
Failure Criteria   bgcolor={{{color}}}}}| 

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=OC5
 |linksto=OC5:FeatureTest-Supports Combining Claims Requested with scope and claims Request Parameter
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Supports Combining Claims Requested with scope and claims Request Parameter/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-56)Supports Combining Claims Requested with scope and Request Object" 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.