- A signed copy of the Certification of Conformance (docx) (PDF) naming that profile. This should use the filename
OpenID-Certification-of-Conformance.pdfin the submitted results. (A different extension such as .jpg for the scanned document may be used as appropriate.)
- A copy of the Certification Terms and Conditions document accompanying the Certification of Conformance. This must use the filename
OpenID-Certification-Terms-and-Conditions.pdfin the submitted results. (This document is not signed but is included for completeness since it is referenced from the Certification of Conformance.)
- Signed Test log files, downloaded from the test suite, for each test in the test plan. These can be downloaded using the ‘Download All Logs’ button on the test plan page. The original filenames for the log files should be retained.
- Client side log files, from the RP side. These logs should include necessary details about the client side application flow.
- A text file with the filename
OpenID-Certification-plan-url.txtcontaining the url for the test plan results page.
- Please note that the full supplied log files will be published as part of a successful certification and these may contain private keys, or other potentially sensitive data, that are part of the test configuration, so it is recommended to deactivate clients / revoke keys prior to submitting your results.
The certification package should consist of a single .zip file containing all the files and using the paths above. The filename should contain the name of the organization, the software being certified, the profile being certified to, the client authentication type and the current date. For example, a certification request by the ProseWare organization of its “Humongous Identity” software for the RP FAPI-RW profile, second implementers draft, using OAuth MTLS client authentication on April 1, 2019 should use a filename like
ProseWare-Humongous_Identity-RP-FAPI-RW-ID2-OAuth-MTLS-1-Apr-2019.zip. If you instead tested with private_key_jwt client authentication, the filename should be like
- Name of Entity (“Implementer”) Making this Certification: ProseWare
- Software or Service (“Deployment”) Name & Version #: Humongous Identity 3.14159
- OpenID Connect Conformance Profile: RP FAPI-RW ID2 OAuth-MTLS
- Conformance Test Suite Software & Version #: www.certification.openid.net 3.2.1
- Test Date: November 1, 2019
- Authorized Signature: HQB
- Name: Harry Q. Bovik
- Title: Senior Computer Scientist
- Date: November 1, 2019
- Implementer’s Name: Jane Doe
- Implementer’s Title: Programmer Extraordinaire
- Implementer’s Phone: +1 (412) 555-1234
- Implementer’s Email: email@example.com
- Implementer’s Address: 5000 Forbes Ave.
- Implementer’s City, State/Province, Postal Code: Pittsburgh, PA 15213
- Implementer’s Country: United States of America
The conformance test suite software version number can be found at the bottom of the homepage after logging in, and is also present in JSON log files.
The certification package must be sent to the OpenID Foundation as an attachment at firstname.lastname@example.org.
The subject line of the e-mail request should be along the lines of “Certification request by ProseWare of Humongous Identity for the RP FAPI-RW ID2 profile”. If receipt of the submission is not acknowledged within two days (or three days if over a weekend), feel free to inquire about whether it was received by e-mailing a message without the attachment (to keep the size of the inquiry small) to email@example.com, cc’ing firstname.lastname@example.org.
A fee is required for FAPI OP certifications. See the OpenID Certification Fee Schedule page for more information. Please pay for your certification application at the Certification Payment page before you make your submission. The OpenID Foundation policy is that certification submissions will only be validated (and, if correct, published) after receipt of payment.