Shibboleth Developer's Meeting, 2021-01-15

Brent

• Jira Legacy
  server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-82

  
  
  • Mostly done.  The only remaining major piece is sorting out how the encryption configuration and parameters resolution pieces will work.

• Jira Legacy
  server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-118

  • Mostly done. Finalizing how we will deal with "metadata" about known and supported named curves.  Right now there's a registry like the one we have for algorithm descriptors, loaded via the Service API.

...

• Jira Legacy
  server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-17

  • Renamed/repackaged with the following logic:
    • POMs: org.geant : idp-oidc-extension-(parent/api/impl/distribution) -> net.shibboleth.oidc : idp-plugin-oidc-op-(parent/api/impl/distribution)
    • Java: org.geant.idpextension.oidc -> net.shibboleth.idp.plugin.oidc.op
  • Some code moved to java-oidc-common, see JCOMOIDC- 6 / 7 / 8

• https://issues.shibboleth.net/jira/browse/

  Jira Legacy
  server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-15

  • Testing the new configuration style on a 4.1-SNAPSHOT deployment

Ian

John

• Fixed some bugs in cpp-linbuild. Working with CentOS 6, 7, and 8 now.
• Trying to produce a usable Docker image from SLES. So far unable to install packages inside the container despite following published docs.

Marvin

Phil

• Finished the DuoOIDC docs - DuoOIDCAuthnConfiguration - subject to scrutiny. 
• Updated the plugin archetype to meet the current working spec (and some other boilerplate) Plugin Archetype
  • Still not sure if anybody will find that useful. I think I would.
• Need to get back to finding some test users.
• Need to spend some time with the oidc-commons.

Rod

• Buried elsewhere
• Looking for low hanging fruit for 4.1
• NOTA: still have a lot of "Installer in a Module/Plugin world" cases open pending getting the experience on the ground.

Scott

• Proxying improvements
  • Direct consumption of upstream Attributes for user identity, replaces awkward attribute resolver settings
  • Hooks outbound and inbound to customize/validate messages
    • Added MessageHandler that runs an injectable function, getting around the problem of declaring an "optional" MessageHandler, same trick could work for Actions
• Finished tabifying resolver and metadata docs

• Jira Legacy
  server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1735

• Jira Legacy
  server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key SUPPORT-218

  • Possible JPA regression, particularly confused by exception leak
• SP call, put on agenda

Tom

• patching
• working on some AMI automation and Jenkins Pipeline research

...