Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Shibboleth Developer's Meeting, April 19, 2013

Attendees: Tom, Scott, Brent, Ian, Daniel, Marvin, Paul

Call Administrivia

Next call is next Friday.

60 to 90 minute call window.

Brent

 

Daniel

RdbmsDataConnectorBeanDefinitionParser supporting Spring IOC config and the v2 schema.

Ian

XmlSecTool 1.2.0 released, huzzah!

That's probably about it for this month.


Marvin

Engaged Scott on dev list when Webflow topics come up. Next week I hope to rework some of the CAS protocol flow actions with the new AbstractProfileAction components.

 

Rod - Apologies
  • Held up by illness.
  • All parsers for AttributeDefinitions have been checked in.
  • Some work needed wrt to eventual loosening of the schema needed
  • ValueMapping definition still outstanding, needs some design, expected this week.
  • I will circulate a proposal about class names for the parsers and tests.
  • Next week.  Finish parsers for Attribute definitions.  Move on to the Static, computed, and Stored Data Connectors, thence back to filters.

 

Scott

2.4.0 release uneventful apart from a few POM mistakes. Not much feedback so far, still have some feature documentation to complete. Noted one or two more things I would have cleaned up, but nothing big.

Updated ant-extensions back to parent-v3, don't know if that will be used. Presumption is any more patches for V2 will just use the 1.0.0 version I pushed.

Tested use of prototype beans in web flow actions successfully, proposed an execution model for our actions based on AbstractAction class in SWF. Error handling being dicussed on list.

Q: Do we need to trap all exceptions we want to use for signaling SWF transitions? Seems like we do. Suggest we adopt automated translation of exception class name into event ID (think Tom proposed this already at some point).

Q: Currently using absence of EventContext to signal "proceed" from OpenSAML actions. Less code but probably not so nice for explicitness, change back to explicit EventContext?

Discussing relationship between actions, handlers, decoders/encoders with Brent on list. Agree that with current breakdown we'll be migrating some actions into handlers. Can work on building action wrappers we need for some of this.

Will spend today sketching out ideas for context objects to use for some of the important system components like authentication and sessions so Brent and I can review next week.

Tom

Worked through some installation, configuration, and upgrade ideas.

Topics

 

Decisions

Coding convention : getLdapUrl or getLDAPURL

Tabled for further discussion.

  • No labels