Shibboleth Developer's Meeting, 2016-06-03
Call Administrivia
10:00 Central US / 11:00 Eastern US / 16:00 UK
Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 1 July. Any reason to deviate from this?
60 to 90 minute call window.
This week's call will use the Lync system at OSU. To participate, call:
- +1 (614) 688-1800 (please use if possible)
- +1 (800) 678-6114 (use only if you're charged for the 614 number)
The Conference ID is: 738127#
https://meet.service.osu.edu/cantor.2/SKDJOISU
International participants should be able to access the 800 number without charge through Skype.
AGENDA
Add items for discussion here
- Proposal to cancel 17th of June call, therefor next call would be 1st of July
Attendees:
Brent, Tom, Scott, Ian, Daniel, Rod
Brent
Daniel
Ian
- xmlsectool beta 1 is being tested, no problems reported so far
- want to release before end of June to allow overlapwant to make a Maven site, some wrinkles around thatif possible
- outstanding issues:
- Maven site, whether to bump parent POM used
- would need a parent POM release
- could do it without, with some compromises
- ECDSA now needed for unit tests, fails under OpenJDK
- can fix, I think:
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key XSTJ-44 - how do OpenSAML and the IdP deal with this?
- can fix, I think:
- Maven site, whether to bump parent POM used
Marvin
Rod
- IdP 3.2.1.1 is probably good to go. Sara will look at it with SSLLabs.
- Bootstrapping myself through the SP.
Scott
Tom
...
- Progress on MFA flow
- Working through SP backlog, hoping for a June release
- Update for TNC, will circulate slides
Tom
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-865 - Suppress vs rename ? Use "this" prefix for API-breaking constructor changes ?
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-73 - Can build with Java 8 now, minus Cobertura report
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-60 - java-support done in private branch, like to get stack done next week
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-85 - java-support done, like to get stack done next week
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key INFRA-110 - links ? Add java-support, spring-extensions, version properties to parent-v3 POM ?
- Testing with Jetty 9.3.9 on Win and Linux
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-843 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-983 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-923 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-993 - tag and release java-idp-example-jetty-base ?
Other