Concordia & interoperability
The areas that were identified as A-priority tasks represent some major issues facing deployers and are worth listing (details are available in the meeting notes):
- IdP discovery
- WS-Federation/SAML metadata lessons
- WS-Federation/SAML metadata distribution and lifecycle
- Interop endpoints
Already there has been some progress in the telecon of 9 October. So, for people interested in interoperability issues, it’s worth keeping an eye on the work.
A colleague presented a use case at the September workshop covering the work being done in New Zealand. One of the interesting things, from my perspective, was to see how the roadmap has evolved to cover a wider range of identity attributes with parallel increase in use of the Liberty Alliance specs.
I thought the final slide was interesting as it examines the case for convergence over interoperability. Both Concordia and the industry in general has settled for interoperability but my colleague made some excellent points why the goal of convergence still remains important to deployers:
- “Interoperability solves a business problem today, but…
– Ongoing fight against divergence
– Requires Interop elements (explicit or implicit)
– Creates future work to manage
– Difficult to manage across organisational boundaries
- Convergence prevents business problems tomorrow…
Having said that, it’s probably fair to say that out-of-the-box interoperability between identity protocols is a difficult enough (but worthy) immediate objective.