version 3 update on wiki and TNC2014

[Scott Koranda]

>>
>>that v3 has a Q3 2014 estimated completion date listed. Do you feel
>>that is still accurate?
>
> That's the target, but I think we're planning around Q4 to be safe. The
> original projection in 2012, after Chad left, was Q2 2014, so given the
> incredibly small number of FTE working on this and the scope of the
> effort, I'm very comfortable with the progress and the amount of slippage.

Understood.

> All I can say about logout is that once Chad left, any promises to do more
> than replicate V2 functionality pretty much ended. What was added to 2.4
> was done with the understanding that it would need to be included in 3.0,
> but that doesn't include that SOAP functionality.
>
> However, the session cache has been done for a while, and is capable of
> tracking and lookup of sessions properly for logout if it's stored
> server-side. The only reason we couldn't include back channel logout
> support is if the SOAP client support, which has never been used by the
> IdP really at all, turns out not to work well. Otherwise it's too simple
> not to include. It just won't do much good for most applications.
>

Thanks.

I am seeing that a common pattern for research organizations is that most
if not all applications do not have a controlling session and removing the SP
session is effective. Further many of these organizations control the primary
IdP used, usually by organization members, and the SPs  are comfortable
configuring to support back channel operations.

So back channel logout support would be useful--granting that it would not
solve all issues.

Thanks,

Scott K