Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

John

Marvin

Phil

  • Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdf52c7d31-6eab-3f0e-93c3-231b5754d506
    keyJPAR-178
    https://shibboleth.atlassian.net/browse/JPAR-178 updated this. Seems OK - at least for now.

  • Working on RP:

    • Profile configuration hookup (OIDC.SSO for now)

    • Message Encoders. Proposed to borrow the ideas used in the SpringAwareMessageEncoderFactory but for OAuth ResponseModes and RP authn request. In Jira LegacyserverSystem JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdf52c7d31-6eab-3f0e-93c3-231b5754d506keyhttps://shibboleth.atlassian.net/browse/JCOMOIDC-27

  • Work on commons:

Rod

...

  • SP 3.3

    • Would be nice to figure out if it’s “safe” to build these on an M1 Mac at some point.

    • Package signing was an issue, ended up tunnelling GPG up to the server after uploading

      • Maybe look at doing the signing from within the Docker images somehow? Probably pretty hard to pull off.

    • Already one minor bug in the deprecation logging, waiting for more bugs before I release a patch.

  • Started reviewing code for OAuth client_credentials grant and JWT token work

    • General comment: there’s a ton of very complex machinery and token bloat built around the “avoid resolving some attributes on the backchannel” issue. We never even bothered to deal with this in SAML and it was never that big a concern that I’m aware of…was this a big enough concern to warrant all that effort and technical debt? Maybe moot I guess.

Tom

Other