I4:FeatureTest-OpenID 2.0 Relying Party openID 1.1 delegations via rel links
From OSIS Open Source Identity Systems
| list help copy as XML edit |
| Feature Test | OpenID 2.0 Relying Party openID 1.1 delegations via rel links |
| Test Type | OpenID Authentication |
| Identifier | FTR-orp-auth-6 |
| Description | Tests OpenID RP's parsing of openID 1.1 rel links. |
| 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 2.0 Relying Party openID 1.1 delegations via rel links | OpenID Relying Party | interop |
- Open the result page for your solution and this test.
- Add the entry <link rel="openid.delegate" href="http://example.myvidoop.com" />
- to the HEAD section of your openID HTML document
- Change the <link rel="openid.server" href="https://myvidoop.com/openid" /> to the appropriate one for the delegated OP.
- You need to remove the openID 2.0 sep so it will not be selected.
- Open the OpenID login page for your relying party.
- Enter your openID such as http://test.myid.com
- After you submit the openID in the login box, you should be redirected to the OpenID provider for your delegated openID.
- Sign into the OpenID Provider using the password for the delegated name.
- This should redirect you back to your relying party site.
- At this point you should be either logged in or told that your OpenID is not registered,
- You should get a message like "verified http://test.myid.com as your identity"
- 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.
- Set outcome in the results page:
- If the success criteria was met, set the outcome to "Works".
- If the test failed, set the outcome to "Failed" and enter information about the failure in the Notes section.
- If other issues occurred set the result to "Issues" and describe them in the Notes section.
- Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
- Update the Date Tested, Browser, and Operating System lines of the results page.
