Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Shibboleth Developer's Meeting, 2019-07-19

Call Administrivia

09:00 Central US / 10:00 Eastern US / 15:00 UK / 17:00 FI

Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2019-08-02. Any reason to deviate from this?

60 to 90 minute call window.


Call Details

This week's call will use the Zoom system at GU, see ZoomGU for see ZoomGU for access info.


AGENDA

Add items for discussion here

  • (Phil) Around for the first 45 mins. Can discuss Anti-CSRF implementations if there is time (CSRF Mitigation Options)
  • CI status / open issues
  • SameSite status
  • Jira Legacy
    serverShibboleth JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyIDP-1450

Attendees:


Brent

  • Out last nearly 2 weeks for conference and PTO.
  • Jira Legacy
    serverShibboleth JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyIDP-1461
    • Velocity 1.7 branch functionally complete; 2.1 just needs fixing up 1 more class.
    • Still pending:
      1. a handful of missing unit tests
      2. SLF4J conversion
      3. style adjustments for Velocity conventions (tabs → spaces, etc).
      4. decision on whether to try to support Velocity 1.7 with another branch/artifact


Daniel


Henri

  • On vacation, unable to attend the call today
  • Updated the Wiki page regarding OIDC RP as EntityDescriptor: /wiki/spaces/DEV/pages/1177321591
    • The plan is to use EntityDescriptor (client_id is entityID), UIInfo (for instance client_name is UIInfo/DisplayName) and custom role descriptor. The table of claim/XML-element relationships and the initial draft of the XML schema can be found from the page.
    • The implementation still in progress: extended SAMLPeerEntityContext and SAMLMetadataContext are exploited by the actions.

...

  • Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyJPAR-142
  • Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyJPAR-143


Marvin


Phil

  • In addition to view and form based CSRF protection, looked at a simple AccessControl mechanism for the RESTful admin endpoints: API Key Access Control


Rod

  • Travel

Scott

  • Work on web site "emulation" and drop down menu, see Contact the Shibboleth Project
  • Jira upgrade
    • Note emails are slightly different to allow for batching of update notifications
  • Documenting attribute registry - AttributeRegistryConfiguration
    • Still making adjustments to configuration e.g. map to propset, slightly simpler XML
  • Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyIDP-1474
    • Relearned how schema lookup works in Spring, documented that a bit for posterity in V4 Spring design page

Tom

  • AWS
    • All multi- tests
    • How to update Java
    • Probably will be stormy/unstable for awhile

Other