[Openid-specs-ab] FW: The fifth OpenID Connect interop (OC5) is now under way!
Mike Jones
Michael.Jones at microsoft.com
Sat Jun 29 11:13:01 UTC 2013
Yes, you can participate in tests with just the MTI requirements. You’ll just need to publish the information on your endpoints and how to register clients.
If you have an OP to test, please let me know this information and I’ll add your implementation to the interop!
-- Mike
From: Torsten Lodderstedt [mailto:torsten at lodderstedt.net]
Sent: Saturday, June 29, 2013 2:15 AM
To: Mike Jones
Cc: openid-specs-ab at lists.openid.net
Subject: Re: [Openid-specs-ab] FW: The fifth OpenID Connect interop (OC5) is now under way!
Hi Mike,
are there plans to support tests for OPs "just" compliant to the MTI requirements (http://openid.net/specs/openid-connect-messages-1_0-20.html#ServerMTI)? Currently, the test requires
discovery and dynamic registration, which are not MTI.
Regards,
Torsten.
Am 27.06.2013 um 00:00 schrieb Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>>:
From: Mike Jones
Sent: Wednesday, June 26, 2013 3:00 PM
To: openid-connect-interop at googlegroups.com<mailto:openid-connect-interop at googlegroups.com>
Subject: The fifth OpenID Connect interop (OC5) is now under way!
Go to http://osis.idcommons.net/wiki/OC5:OpenID_Connect_Interop_5 or http://osis.idcommons.net/ to begin participating.
Please enter your cross solution test results at http://osis.idcommons.net/wiki/OC5:Cross_Solution_RP_x_OP_Results and your feature test results in the table for the solution. Links to current solutions participating are at http://osis.idcommons.net/wiki/Category:OC5_Solution.
A few notes on the differences in the solutions between OC4 and OC5:
· Google’s entry is now for their production deployment. Please be sure to test with this!
· The AOL Equinox entry has been temporarily removed, pending needed updates.
· The PingFederate entry has been temporarily removed, pending needed updates.
· The IBM Prototype entry has been removed for now, due to resourcing issues.
You must be logged into the wiki to record results. Send me e-mail if you need to have an account created. (Or use an OpenID 2.0 identifier to log in.)
If you run a test for a solution, record the test result by clicking on the “Not Tested” link next to the test. This should take you to a page like http://osis.idcommons.net/w/index.php?title=OC5:FTR-op-rtyp-idt-x-Google_Deployment.
Currently there’s a bug in the interop wiki software you’ll need to know how to work around. When you click on a red “Not Tested” link, the page is supposed to be automatically created. Instead, you’ll see an error message that begins “The database did not find the text of a page that it should have found”. The way to work around this bug is to click on the “edit” tab at the top of the error page. This will bring up the result page for you to edit. Record the result and save the page.
Change the outcome to one of “Works”, “Failed”, or “Issues”. If the result is anything but “Works”, also record a description of the behavior observed in the notes section of the results page. Also, update the testedby and testdate fields and if applicable, the operatingsystem and browser fields.
If a test fails or has issues, either contact the participants directly using the information on their participant page or send a note about the failure to the openid-connect-interop at googlegroups.com<mailto:openid-connect-interop at googlegroups.com> list, or both. If any of you have problems recording test results, feel free to drop me a note and I’ll help out.
Happy testing!
-- Mike
_______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-ab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130629/f1bacf17/attachment.html>
More information about the Openid-specs-ab
mailing list