Meeting Invitation
Topic: Error Handling WG
Time: Mar 12, 2020 12:00 PM Pacific Time (US and Canada)
Every week on Thu, until Mar 19, 2020, 5 occurrence(s)
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://zoom.us/meeting/uJItd-GhqTor_piZ0ZQbAGlpqS9B-ipwVg/ics?icsToken=98tyKuyurjsiE9OUsVz9e7ItW6vlb8_ukE5eo5kNpi7nIgdfchLFb8APO6JoJt-B
Join Zoom Meeting
https://zoom.us/j/560089711?pwd=YktsRVBCKzJXdnlsZGwwZExydUN4UT09
Meeting ID: 560 089 711
Password: 591162
One tap mobile
+16699006833,,560089711# US (San Jose)
+19292056099,,560089711# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
Meeting ID: 560 089 711
Find your local number: https://zoom.us/u/aRjU5ChSJ
Join by Skype for Business
https://zoom.us/skype/560089711
Attendees
Regrets
Agenda
Working Document - Use Cases and Errors
- Demo SP (SWAMID)
- There is now a demo php-site up for the errorURL: https://ladok3.its.umu.se/errorurl-demo/
- The code is at https://github.com/fredrikdomeij/errorurl-demo
- Wrap up technical requirements
- Next steps - writing this up for public comment
Notes
Demo SP (SWAMID)
- There is now a demo php-site up for the errorURL: https://ladok3.its.umu.se/errorurl-demo/
(This is not a full SP; just an application example) - The code is at https://github.com/fredrikdomeij/errorurl-demo
What is the behavior if one of the tags is not included or the IdP does not support it? They should all be considered optional.
Wrap up technical requirements
What we have is sufficient for community comment
Next steps
Complete demo php-site with good examples so we have a reference implementation for people to consider. Should also do some visual distinction to show which part is for the SP, which for the IdP. Maybe a flow diagram?
Alan Buxey (and hopefully Scott Cantor ) will work on where we need to create appropriate text for the error messages (see config.php
Fredrik Domeij will give people the necessary GitHub repository access as needed)
Write this up for public comment;
This is going to cover both a technical component as well as descriptive text
This will go out through the REFEDS community consultation process
Fredrik Domeij and Andrew Morgan will work on drafting the official proposal; Heather will check in on Tuesday to see where we stand, and whether we should have a call on Thursday to discuss.
Heather to add three more weeks for the WG