Shibboleth Developer's Meeting, 2020-06-05

Brent

Daniel

Henri

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

  
  
  • MDDriven profile configurations working as expected
    • Will check with 

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

       next week
  • Added ClientSecretReferenceKey -element to the schema
    • Simple resolver interface extending Resolver<String, CriteriaSet>
    • Initial implementation for Properties resource
      • How to make it refreshing whenever metadata provider is refreshed?
    • Other implementations? Perhaps HTTP (using the approach from HTTP data connector)?

Ian

• (Maybe an agenda item) Thread safety is hard:
  • Arises through 

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

    ; full discussion there.
  • A lot of things we say are @ThreadSafe really aren't, although they are mostly @ThreadSafeAfterInit and other things probably conspire to mean we're probably OK in practice. This makes me uncomfortable.
  • It's not possible even in principle to make most things truly @ThreadSafe because of 

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

    .
  • We could fix that (and I think we should, see this commit) but that wouldn't address all the issues, just make it possible to do so for cases we care most about.
  • Beyond that, I don't think really nailing this down is going to be felt to be worthwhile, but we might want to document some assumptions and change some annotations anyway.
• Building from Docker containers: iay/shibboleth-build-docker seems to work

...