Shibboleth Developers

["Scott Cantor" <>]

> I just noticed that calling doCheckAuthN(true) will call doHandler() if
> it is needed. This way can we avoid having to call doHandler() ourselves
> assuming that every request passes through here?

That isn't really why it's checking the URL. Calling the handler that way is
simply a shortcut, and it doesn't even happen on most platforms. The main
issue is preventing the check functions from blocking access to the handler.

> Is this too difficult to implement?

For me, almost certainly. I know threads very well and I don't use
asynchronous designs pretty much ever, so I'm probably not the person to do
it.

I don't see how you could ever expect to get control back or track all the
state you would need to preserve to get back in and pick up where it left
off. It would pretty much require starting over from scratch because all the
work would need to be moved into task queues, I think.

Here's a different option...drop shibd out, use the MemoryListener alone
without the remoting layer, and only deploy it using the POST profile with
no callbacks...

> Can I do this electronically? Print, sign, scan and send it 
> to somewhere?

I assume so.

-- Scott