Shibboleth Developer's Meeting, 2021-05-07

Brent

Daniel

Henri

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

  • Deep dive into the attribute registry & transcoders

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

  • In practise the Nimbus release-cycle means that if we need a bug-fix, it's always a minor update for us 

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

  • About half is done with the latest Nimbus dependencies, I don't foresee issues

...

Lots of minor changes for the next minor/major release.  Two open questions

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

  • Do we have the right to change the default behavior of the Attribute Resolver wrt Display Information(especially given that no-one will notice)?
  • This would allow us to actively deprecate & log as deprecated a lot of old methods which are there solely to support IdPAttributes carrying DIsplay Information.

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

  • There is an impedance mismatch between the CLIs (which use System.out.println) and much of the installers (which need to have the ability to log verbosely).
  • How to square the circle?

...