Page Comparison

...

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

  • Propagation: found a way to control the front-channel propagation result in UI

    • The propagation flow calls the RP’s front-channel logout URI in yet another iframe, but proceeds itself into the similar end-state as back-channel does

  • RP-initiated logout:

    • Mostly done now, also including some initial flow tests (first flow test for me with a flow resuming from a view)

    • Some fine-tuning needed for id_token_hint validation (first case when OP is validating its own signatures)

Ian

John

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

  • Eventually prevailed. Short version: found no way to do this without a subscription; and, winner of the WTF-of-the-month award, RHEL AMIs ship with a non-obvious, non-default (by Red Hat’s own definition) setting that disables full RPM repos on subscribed machines.

  • I have a patch for the make $COMPONENT regression that affects the curl-openssl component. Working on test builds for that today.

Marvin

Phil

• Not overly productive, but…

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

  I hacked it, but maybe that can work, tbc.

• Started looking at a webauthn authentication plugin.

  • Basic plugin structure created and committed.

  • Also, some more minor cleanups to the archetype.

...