Shibboleth Developer's Meeting, 2020-06-05
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 2020-06-19. Any reason to deviate from this?
60 to 90 minute call window.
This week's call will use the Zoom system at GU, see ZoomGU for see ZoomGU for access info.
AGENDA
- PKIX root behavior
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-1583 - Opening up master branches
- Ian Young's thread safety thing, see below
Attendees:
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
next weekJira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1608
- Will check with
- 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)?
- MDDriven profile configurations working as expected
...