Skip to content

2025‐09‐02

Aaron Parecki edited this page Sep 2, 2025 · 1 revision

IPSIE WG Meeting Minutes

Date: 2025-09-02

Attendees

  • Aaron Parecki (Okta)
  • Dick Hardt (Hellō)
  • Karl McGuinness
  • Shannon Roddy
  • Bjorn Hjelm
  • Mike Kiser (SailPoint)
  • Jen Schreiber
  • Buster Doney
  • Kenn Chong (RSA)
  • Jeff Bounds (SailPoint)
  • Bjorn Hjelm (Yubico)
  • George Fletcher (Practical Identity LLC)

Agenda

Notetaker: Jen Schreiber, George Fletcher

Notes:

  • Ask WG to review Interop Testing Checklist this week
    • https://github.com/openid/ipsie/blob/e71ca02d306590f6a3ba817515c6289a7d87378d/2026-01-interop-testing.md
    • Goal is concrete and testable statements from the OIDC Profile
    • Separated Idp vs Rp requirement checklist
    • Dick suggested adding clarification for what is pass vs fail is (and include pos and neg tests)
    • George: For the event, is there an expectation that an RP/Idp is written that can do all the pos/neg test cases?
      • Aaron: that is the ideal scenario but might not be realistic by Jan.
    • split the check list into IDP positive, RP positive, IDP negative, RP negative
    • need to test that the insecure mechanisms are not working
    • generally IDPs and RPs showing up to the interop event will be focused on the happy paths
    • shared signals interops focused on the happy paths and then when things failed identify the issues
    • current checklist is very useful for conformance testing; may need to be filtered for the interop
    • Recommendation to focus on the protocol and describe what the expected behavior is
    • WG live edit of the checklist doc to remove the negative tests
    • conformance to TLS 1.2
      • really an IDP requirement - the IDP should not allow TLS connections that are not TLS 1.2 or above
      • if the RP attempts to connect to an IDP using TLS 1.2 and the IDP doesn't support TLS 1.2 or later, the RP should fail the connection
    • focus on the profiled parts of the specs/protocols as that is what is different from today
    • look at messages on the wire to confirm whether the IDP/RP are meeting the profile
    • feedback from shared signals interops
      • Just as an example - linking back to the spec was helpful for all of us - also note that there was a lot less for the receiver than the transmitter
      • BBBCDA3A-A7E4-4280-9513-8EB4764DEC1E.jpg
      • 079C17A1-C2BC-47CB-BA4D-7A5F4433DD37.jpg
    • Aaron updated the checklist to focus on the positive behaviors and spec profiling
    • Recommendation to request conformance tests from the OpenID Foundation
    • an RP running at IPSIE SL1 profile, must fail a response that does not conform to the IPSIE SL1 profile
    • validation of IPSIE profiles in the first interop can be done through debug logs/wire captures.
Clone this wiki locally