Shibboleth Developer's Meeting, August 9, 2013

...

• Did the schema validation thing.
• Did the spring bean config for  the attribute mapper
• Rest of the week spent in a cleanup pass over attibute-filter for Tom.
• Next up:
  • Cleanup pass on Attribute Resolver
  • Auto generate Attribute mapper config
  • Topical bug fixing
  • TOU/Attribute release.
  • Resources - us vs spring vs ??
  • getLDAPURL
  • More attribute filter documentation?
    
  • ????

Scott 

Attempted aborted wiki upgrade, ran into significant issues. Identified one possible problem with the plugin manager that was corrected, will need to go back and start testing from scratch on VM.

Rest of time was spent on the "end" stages of the authentication flow:

• adding custom information to Java Subject
• canoncializing Subject into principal name string
• detecting an identity switch between active session and a new result
• creating the SubjectContext as the output of the process

With more pieces done, seams are showing and need to work more on error handling/tracking, and how the flow would control which type of custom Principal would be added to the Subject. For example, a flow allowing password and MFA at the same time via one UI needs to know how to decide which actions to run, and what custom AuthenticationContextClassRef to attach.

Considering how best to integrate SubjectCanonicalizer notion into existing use cases like PrincipalConnector in V2.

Tom

The primary task on my mind is performance testing. I currently do not have any sort of harness set up to examine Web Flow, and I think I should. An example would be to try and measure if there is a discernible impact on performance or cpu for stateless vs stateful action beans. My hypothesis is that I will not be able to discern much difference, but the test harness itself would be worthwhile, to me.

...