I5:FeatureTest-OpenID Relying Party support for account creation via Simple Registration

From OSIS Open Source Identity Systems

Jump to: navigation, search

   list help  copy  as XML  edit
Feature Test   OpenID Relying Party support for account creation via Simple Registration
Test Type   OpenID Authentication
Identifier   FTR-orp-sreg-2  
Description   Tests OpenID Relying Party support for account creation via Simple Registration  
Role tested   OpenID Identity Relying Party  
Known Successful Reference Solution(s)  
I5:Plaxo Signin  
Success Criteria   OpenID authentication succeeds RP asks for and receives sreg information pre-filling the account creation form.  
Failure Criteria   OpenID not accepted or other failures  

Features Proven

Feature feature_type solution_role
OpenID Relying Party support for account creation via Simple Registration OpenID Relying Party usability

Instructions

  1. Open the result page for your solution and this test.
  2. Open the test Page http://test-id.org/RP/SregAccountCreation.aspx and find the openID in another Tab
  3. Open the OpenID login page for your relying party.
  4. Copy the OpenID from the test page into the OpenID login field of the page.
    1. This ID provides sreg values and will not ask for a password.
  5. You will be retuned to the test page.
    1. This will report the SREG attributes the RP has requested.
    2. Required attributes will have a * beside the name.
    3. You can edit the return values as you like for testing.
    4. If no attributes are asked for this is a failure
  6. Click on "Continue" to submit the claims
  7. The account information should be populated from the sreg information, this is a successful outcome.
  8. If you are prompted to create a new account but the fields are not pre-filled this is a "Not Supported" outcome..
  9. Set outcome 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.
  10. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
  11. Update the Date Tested, Browser, and Operating System lines of the results page.
Personal tools