Shibboleth Developer's Meeting, 2020-03-20

Call Administrivia

09:00 Central US / 10:00 Eastern US / 14:00 UK / 16:00 FI

Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2020-04-03. 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 access info.

AGENDA

AI for somebody to redeploy the IdP site and check the javadocs
Work left on testing infrastructure?
1. Move on-commit jobs off host
2. Prioritize moving Jenkins to AWS first when new server is established.
Development priorities
1. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key OSJ-82
2. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1473
3. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1454
4. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1392
5. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1126
6. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1014
7. Jira Legacy
  server Shibboleth JIRA
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key IDP-1015
8. Duo / OIDC plugin, I think no issue filed yet
  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-1588

Brent

Daniel

Henri

No development after OIDC v2 yet
Planning to continue OIDC/SAML metadata work again next week (on hold since Dec)
- New feature branch or change master to 2.1.0-SNAPSHOT?
- If we want to use XML namespace urn:mace:shibboleth:metadata:*, XMLObject -related stuff should probably go to idp-saml-api + -impl?

...

Versions Compared