I4:FeatureTest-OpenID Relying Party Accepts Namespaced openID 1.1 delegations in XRDS documents

From OSIS Open Source Identity Systems

list help  copy  as XML  edit

Feature Test	OpenID Relying Party Accepts Namespaced openID 1.1 delegations in XRDS documents
Test Type	OpenID Authentication
Identifier	FTR-orp-auth-7
Description	Tests OpenID RP's parsing of XRDS documents
Role tested	OpenID Identity Relying Party
Known Successful Reference Solution(s)	I4:JanRain PHP I4:Plaxo Signin
Success Criteria	The RP uses the delegated openID
Failure Criteria	The RP uses input openID or Error

Features Proven

Feature	feature_type	solution_role
OpenID Relying Party Accepts Namespaced openID 1.1 delegations in XRDS documents	OpenID Relying Party	interop

Instructions

1. Open the result page for your solution and this test.
2. Add the entry <openid:Delegate xmlns:openid="http://openid.net/xmlns/1.0"> http://example.myvidoop.com</openid:Delegate>
3. to your XRDS file replacing example delegated name with one you control.
4. Change the URI to the appropriate one for the delegated OP. This needs to be in the openID 1.0/1.1 sep.
5. You need to remove the openID 2.0 sep so it will not be selected.
6. Open the OpenID login page for your relying party.
7. Enter your openID such as =my.name or @freeid.myid into the OpenID login field of the page.
   1. If you don't have an i-name, you can obtain a free i-name from http://freeid.net/register or http://www.freexri.com/
   2. These iname sites let you edit your XRDS, not all URL based openID OPs support XRDS editing.
8. After you submit the i-name in the login box, you should be redirected to the OpenID provider for your delegated openID.
9. Sign into the OpenID Provider using the password for the delegated name.
10. This should redirect you back to your relying party site.
11. At this point you should be either logged in or told that your OpenID is not registered,
12. You should get a message like "verified =Mike.Jones as your identity"
13. Failure would be being redirected to the OP with the input identity rather than the delegated one or the RP throwing an error on parsing the XRDS.
14. 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.
15. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
16. Update the Date Tested, Browser, and Operating System lines of the results page.