Shibboleth Developer's Meeting, 2020-09-04

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-323

  
  
  • Provisional fix committed.  Reporter says seems to fix his issue.  Need to do a little more testing before closing out.

Daniel

Henri

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

  • Digesting the comments from Ian and Scott
  • XML schema: sequence vs choice

Ian

John

Marvin

Phil

• Updated the archetype inline with the 'current' plugin guidance (git@git.shibboleth.net:philsmart/java-idp-plugin-archetype).
• Tried out the plugin installer for my plugin (some logging suggestions

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

  )
• Various Duo plugin fixes.
  • I will probably add some tickets highlighting a few areas for general review next week.
  • Added the Version class and Manifest stuff, but can not get it to work. Will ask Rod. 
• Are we OK with adding detectHandlerMethodsInAncestorContexts="true" to the RequestMappingHandlerMapping in mvc-beans.xml? so my controller is picked up in the postconfig.xml file.

Rod

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

   
  
  • Functionally complete
  • Bug fixing now (including the worrying 

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

    )
  • Will swap in the module stuff and work on integrating it into the scripting  plugins and the installer.

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

Scott

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

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

  • No longer need to teach it about new property files, we will auto-load anything under conf with that suffix.

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

  • An IdPModule is a unit of function that can be individually enabled or disabled via command line.
  • Plugins can expose any number of IdPModules after installation, and could auto-enable them.
  • Generally this just involves managing a set of configuration resources by either copying them in or removing them (usually be saving them off, not deletion, but this will be controllable). Resources can be tagged as replace or noreplace, RPM-style.
  • Most modules should be expressible with property files and a trivial subclass to add to the Java services file.
  • Repeated enable/disable will be idempotent.
  • "Disabled" modules may not be totally "off" but probably will operate with default, often unusable, settings.
  • Many default config files (esp. for various subflows) will be removed or hidden in 4.1 behind disabled modules.
  • Upgrades will act as though many modules are already enabled, and disabling them can be used to remove the files.

...