Shibboleth Developer's Meeting, 2020-10-02

Brent

• OSJ-324 - Getting issue details... STATUS

Daniel

Henri

• Drafted the java-oidc-common project with Phil last week
  • See /wiki/spaces/DEV/pages/1200783544 for the current plan
• Participated to an OIDCfed interoperability event this week
  • Some successful smoke-testing via PoC exploiting a fed-library from NIK-HEF
• Musing ways to enable (OIDC/OAuth2) feature extensions fluently
  • Some have new endpoints (e.g. Device-flow, PAR), some extend the existing endpoints (e.g. PKCE), ...
  • Keep these in mind while refactoring/repackaging into the new plugin/module

Ian

• XSTJ-82 - Getting issue details... STATUS
  
  • In test with selected deployers
  • Wiki space for V3 reorganized, PKCS#11 section rewritten
  • Quick question about parent POM evolution

John

Marvin

Phil

• JDUO-15 - Getting issue details... STATUS
  • Switched from using custom token verification actions to using the Nimbus claims and signature verification.
    • Perhaps should be made more extensible - although it does meet the 'Duo Spec' on what claims to verify. 
• JDUO-17 - Getting issue details... STATUS
  • Added a new Nimbus based Duo Client - so you could now run without the native Duo SDK. 
    • Although it temporarily uses the Auth0 library to sign certain JWTs due to the size limitations of the Duo secret key - which Nimbus enforces.
• Will try out plugin/module usage.

Rod

• Plugins:
  • Further development on hold pending others playing with it.
  • Working with Scott on implementaion details. IDP-1683 - Getting issue details... STATUS  and  IDP-1652 - Getting issue details... STATUS
  • Still an open question around logging vs System.out vs i18N - but this need not be fixed for 4.1
  • Talked to Ian about Nashorn and licensing
    • Made minor changes to the license documents we ship but we are happy that we can ship this under Apache
    • There is an open question about distributing the GraalVM bits
      • We can just bundle them The GraalVM license appears to say this is OK
        We decided to follow this modulo anyone telling that our understanding is wrong.
        We will prefer rhino in our documentation when Java >=15 become important.
      • We can prompt and download during install (which we once thought was a good idea)
      • We can make downloading them into edit-webapp a pre requisitite and blame Oracle's Lawyers
        This will be a fallback
    • I have given up caring. Lets pick one and close this sorry chapter
• Hitting low and slightly less low hanging JIRA cases
  • Notable I18N and the IdP

Scott

• SP
  • Fixed (I hope) a 15+ year old SP bug
    • SSPCPP-906 - Getting issue details... STATUS
  • Fixed another open redirector bug, I'm done treating any of this as a security issue, not rushing out a patch
    • SSPCPP-907 - Getting issue details... STATUS
  • Waiting on a possible segfault issue report (not the config related one that came in 10/1) and then probably will be thinking about a release
• Finished? modularizing core, most conf subfolders emptied out
• Would like to move e.g. all the attribute related service files to streamline root folder but we'd have to special case the upgrader, not sure if worth it
• Additional conversion of "dumb" XML configuration usage into properties
• Started reviewing and suggesting adjustments to plugin design
  • Finishing up initial workk on a property-driven plugin class
  • Set up wiki space for docs, will shortly propose a standard layout for hosting plugins and update info files

Tom

• glacial progress

Other