Shibboleth Developer's Meeting, 2020-10-02

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

...

• Plugins:
  • Further development on hold pending others playing with it.
  • Working with Scott on implementaion details.

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

     and 

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

  • 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 OrackeOracle'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

...