Page Comparison

...

• RDW:

  Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JMVN-68

  • Mostly For locally signed artifacts no longer used (xercesImpl, xml-apis)

  • I am reluctant to remove anything from a Keystore just because it isn't being used right now

  • Ditto keystores themselves.

Attendees:

Brent

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSATTR-6

  • Still coming along. Progress slow over last couple of weeks due to local Project From Hell.

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSMD-11

  • Completed for HTTP metadata resolvers.

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-55

  • We discussed this as an open question and I opened this issue to track.

Daniel

• Nothing to report.

Henri

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-222

  • DynamicMetadataCache (in oidc-common) based trust chain resolution

    • Signature validation via metadata filters (BiFunction -hook)

  • Finishing first prototype for automatic registration via PAR and authorize -endpoints

Ian

• Nothing to report.

John

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key SSPCPP-994

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key SSPCPP-995

Marvin

Phil

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JWEBAUTHN-27

  • Cleaning this up based on feedback.

  • Also cleaning up the registration and management UIs. Credentials can be labelled in the view. e.g.

    • Image Added

  • Once merged into main, I will announce RC3.

• After RC3 is announced, I will switch contexts to work on:

  • WebAuthn Docs

  • the CSRF changes in the IdP

    Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2339

  • Updates to the Native Duo SDK

    Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JDUO-92

  • RP Automated tests against the OIDC conformance suite. I had a call with Henri about this, so I see a route forward

  • Think about HTTP APIs to the WebAuthn registration repository

Rod

• Bug squashing

• Jetty re-org (and fallout). No new testing

• Tracking the CPP code in the windows build

...

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2288

  • Replaced post processors with “property-specifiied class” indirection in Spring parser, deployer-compatible with original design

  • Had to redesign the ByReference metadata filter handling to preserve proper filter order

• SP 3.5 release, smooth apart from some older packaging mistakes

• Design breakdown for SP agent work

  • Native Agent Design/Development Plan

• Branched cpp-sp and started teardown of existing code base

  • Plan is to get as much torn out as possible before working back up to new or replacement code, but keep it building as much as possible.

  • Looking at unit testing to validate new development to defer the need to produce a working agent I can test against Java (same way I tested the Java without a working agent). Boost has a unit testing framework worth looking at.

Tom

• Thanks Henri - OP Conformance Suite tests pass for IdP 5.1.3 and V5

  • still need to work on the logout conformance tests

  • probably should test previous, current, and next versions of the OP plugin with both IdP 5.1.3 and 5.2

• Thanks Rod - Jetty Plugin tests a work in progress

• Back to working on IDP-2323 - consent invalid data

  • as I have mentioned, throwing the JsonException is trivial

    • looking at how that would affect storage record pruning and what to do with that “feature”

Other